[darcs-users] Learning about slurpy
yarcs at qualitycode.com
Sun Nov 16 17:56:31 UTC 2003
I'm trying to completely understand the darcs code for 'add', and I
think I almost have it. But I want to confirm my understanding of a slurpy.
I am not comfortable thinking the way a lazy functional language thinks,
so I'm trying to come up with a non-haskell description of a slurpy.
My impression is that a slurpy is essentially a sandbox. It starts out
as an exact copy of an existing directory structure on disk. You can
make changes to it (add, modify, rename, remove) that will seem real
when viewed through the slurpy, but which do not affect the underlying
directory that it was slurped from.
Hopefully I have this right. It took me quite a while to grasp, partly
because of the 'slurp_current' naming problem that is already identified
in the code as a FIXME. I would suggest a simple rename to 'slurp_pending'.
More information about the darcs-users