resetoperation, which is used when nesting a datatype in a map-datatype. Therefore the details of
resetare explained with the map-datatypes below.
resetoperation, which is useful for embedding the counter in a map datatype.
set-operation which allows to assign a value to the integer.
set-operations and by considering all increments and decrement operations which are not overwritten by the
setoperations, the semantics are equivalent to the counter datatype.
Sbe the set of all concurrent
set-operations, which have not been overridden.
assign(v), take all increments and decrements concurrent to
oand aggregate them onto
set(0). This is not a standard implementation of
resetsince it might affect concurrent updates and does not reset the internal state to the initial state.
enable-operation among the latest operations.
enable-operation and no
disableoperation among the latest operations.
reseton the removed value. Intuitively, a reset-operation Should have the effect of removing all previous operations, so that the state is equivalent to the initial state, but operations concurrent to the
resetare not lost. However, not all datatypes support a
resetand not all follow this principle (usually for performance reasons).
removeon an add-wins map resets the embedded datatype by calling its reset operation. Moreover, it marks the entry as removed, so that it does not show up when reading the value of the map.
removeon a remove-resets map resets the embedded datatype by calling its reset operation.
resetthis is the case for add-wins sets, multi-value registers, fat counters, flags and remove-reset maps which only contain the types in this sentence (read this as an inductive definition). Therefore only these types should be used with remove-reset maps.