An LMVar is a labeled synchronization variable (an MVar) that can be used by concurrent threads to communicate.

Create a new labeled MVar, in an empty state. Note that the supplied label must be above the current label and below the current clearance. An exception will be thrown by the underlying guardAlloc if this is not the case.

Same as newEmptyLMVar except it takes a set of privileges which are accounted for in comparing the label of the MVar to the current label and clearance.

Create a new labeled MVar, in an filled state with the supplied value. Note that the supplied label must be above the current label and below the current clearance.

Same as newLMVar except it takes a set of privileges which are accounted for in comparing the label of the MVar to the current label.

Return contents of the LMVar. Note that a take consists of a read and a write, since it observes whether or not the LMVar is full, and thus the current label must be the same as that of the LMVar (of course, this is not the case when using privileges). Hence, if the label of the LMVar is below the current clearance, we raise the current label to the join of the current label and the label of the MVar and read the contents of the MVar. The underlying guard guardWrite will throw an exception if any of the IFC checks fail. Finally, like MVars if the LMVar is empty, takeLMVar blocks.

Same as takeLMVar except takeLMVarP takes a privilege object which is used when the current label is raised.

Non-blocking version of takeLMVar. It returns Nothing if the LMVar is empty, otherwise it returns Just value, emptying the LMVar.

Same as tryTakeLMVar, but uses priviliges when raising current label.

Puts a value into an LMVar. Note that a put consists of a read and a write, since it observes whether or not the LMVar is empty, and so the current label must be the same as that of the LMVar (of course, this is not the case when using privileges). As in the takeLMVar case, if the label of the LMVar is below the current clearance, we raise the current label to the join of the current label and the label of the MVar and put the value into the MVar. Moreover if these IFC restrictions fail, the underlying guardWrite throws an exception. If the LMVar is full, putLMVar blocks.

Same as putLMVar except putLMVarP takes a privilege object which is used when the current label is raised.

Non-blocking version of putLMVar. It returns True if the LMVar was empty and the put succeeded, otherwise it returns False.

Same as tryPutLMVar, but uses privileges when raising current label.

Combination of takeLMVar and putLMVar. Read the value, and just put it back. This operation is not atomic, and can can result in unexpected outcomes if another thread is simultaneously calling a function such as putLMVar, tryTakeLMVarP, or isEmptyLMVar for this LMVar.

Same as readLMVar except readLMVarP takes a privilege object which is used when the current label is raised.

Takes a value from an LMVar, puts a new value into the LMvar, and returns the taken value. Like the other LMVar operations it is required that the label of the LMVar be above the current label and below the current clearance. Moreover, the current label is raised to accommodate for the observation. The underlying guardWrite throws an exception if this cannot be accomplished. This operation is atomic iff there is no other thread calling putLMVar for this LMVar.

Same as swapLMVar except swapLMVarP takes a privilege object which is used when the current label is raised.

Check the status of an LMVar, i.e., whether it is empty. The function succeeds if the label of the LMVar is below the current clearance -- the current label is raised to the join of the LMVar label and the current label.

Same as isEmptyLMVar, but uses privileges when raising current label.