|Repository IO monad. This monad-like datatype is responsible for
sequencing IO actions that modify the tentative recorded state of
|Gets the unrecorded changes in the given paths in the current repository.
|This fuction is unsafe because it accepts a patch that works on the tentative
pending and we don't currently track the state of the tentative pending.
A PatchSet is in reverse order, plus has information about which
tags are clean, meaning all patches applied prior to them are in
the tag itself, so we can stop reading at that point. Just to
clarify, the first patch in a PatchSet is the one most recently
applied to the repo.
PatchSets have the property that if
(info $ last $ head a) == (info $ last $ head b)
then (tail a) and (tail b) are identical repositories
Does this mean that in a patch set such as [[a b t1 c d e t2][f g
t3] [h i]], t1, t2 and t3 are tags, and t2 and t3 are clean?
Can we have PatchSet with length at least 3?
|Sets scripts in or below the current directory executable. A script is any file that starts
with the bytes '#!'. This is used sometimes for --set-scripts-executable, but at other times
--set-scripts-executable is handled by the hunk patch case of applyFL.
|Similar to the ask function of the MonadReader class.
This allows actions in the RIO monad to get the current
FIXME: Don't export this. If we don't export this
it makes it harder for arbitrary IO actions to access
the repository and hence our code is easier to audit.
|This the RIO equivalent of liftIO.
|Produced by Haddock version 2.4.2|