Every Key.t
in the table has an associated state
, which each job running on that
key gets access to. Jobs maybe have an associated job_tag
which is provided
purely to assist debugging, as the tag is included in the sexp serialization of
t
.
enqueue t ~key f
enqueues f
for key
. f
will be called with the state of
key
when invoked.
Invariant 1: it is guaranteed that f
will not be called immediately.
Invariant 2: if f
raises, then the exception will be raised to the monitor in
effect when enqueue
was called. Subsequent jobs for key
will proceed.
Invariant 3: to avoid race, there are no deferred operations between finding the
state and calling f
with the state found. Otherwise, the user would need to
consider the race that the state passed to f
might have been changed by
set_state
.