|
|
|
|
Synopsis |
|
|
|
Documentation |
|
|
cacheHash computes the cache hash (i.e. filename) of a packed string.
|
|
|
|
|
|
|
Constructors | | Instances | |
|
|
|
Constructors | | Instances | |
|
|
|
Constructors | | Instances | |
|
|
|
Constructors | | Instances | |
|
|
|
Constructors | HashedPristineDir | | HashedPatchesDir | | HashedInventoriesDir | |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
speculateFileUsingCache cache subdirectory name takes note that
the file name is likely to be useful soon: pipelined downloads
will add it to the (low-priority) queue, for the rest it is a noop.
|
|
|
writeFileUsingCache cache compression subdir contents write the string contents to
the directory subdir, except if it is already in the cache, in which case it is a noop.
Warning (?) this means that in case of a hash collision, writing using writeFileUsingCache is
a noop. The returned value is the filename that was given to the string.
|
|
|
|
|
|
|
peekInCache cache subdir hash tells whether cache and
contains an object with hash hash in a writable position.
Florent: why do we want it to be in a writable position?
|
|
|
|
Produced by Haddock version 2.4.2 |