Lines Matching +full:work +full:- +full:around

34 /// in a clean container and in a "safe" work directory that gets cleaned
40 ///    around through the lifetime of the next operations.  Only one
43 ///    track of any per-process data you may need using the returned
57 /// directories: the first is the "work directory", which is an empty directory
58 /// that acts as the subprocess' work directory; the second is the "control
59 /// directory", which is the location where the in-process code may place files
60 /// that are not clobbered by activities in the work directory.
111 /// Objects of this type can be copied around but their implementation is
137 /// and serves as the owner of the remaining on-disk files.  The caller is
138 /// expected to call cleanup() before destruction to remove the on-disk state.
140 /// Objects of this type can be copied around but their implementation is
173 /// Objects of this type can be copied around (because we do not have move