Safe Haskell | None |
---|---|
Language | Haskell2010 |
Allocate resources which are guaranteed to be released.
For more information, see https://github.com/snoyberg/conduit/tree/master/resourcet#readme.
One point to note: all register cleanup actions live in the IO
monad, not
the main monad. This allows both more efficient code, and for monads to be
transformed.
Synopsis
- data ResourceT m a
- type ResIO = ResourceT IO
- data ReleaseKey
- runResourceT :: MonadUnliftIO m => ResourceT m a -> m a
- runResourceTChecked :: MonadUnliftIO m => ResourceT m a -> m a
- data ResourceCleanupException = ResourceCleanupException {}
- resourceForkWith :: MonadUnliftIO m => (IO () -> IO a) -> ResourceT m () -> ResourceT m a
- resourceForkIO :: MonadUnliftIO m => ResourceT m () -> ResourceT m ThreadId
- transResourceT :: (m a -> n b) -> ResourceT m a -> ResourceT n b
- joinResourceT :: ResourceT (ResourceT m) a -> ResourceT m a
- allocate :: MonadResource m => IO a -> (a -> IO ()) -> m (ReleaseKey, a)
- allocate_ :: MonadResource m => IO a -> IO () -> m ReleaseKey
- register :: MonadResource m => IO () -> m ReleaseKey
- release :: MonadIO m => ReleaseKey -> m ()
- unprotect :: MonadIO m => ReleaseKey -> m (Maybe (IO ()))
- resourceMask :: MonadResource m => ((forall a. ResourceT IO a -> ResourceT IO a) -> ResourceT IO b) -> m b
- class MonadIO m => MonadResource m where
- liftResourceT :: ResourceT IO a -> m a
- type MonadResourceBase = MonadUnliftIO
- data InvalidAccess = InvalidAccess {}
- class MonadIO m => MonadUnliftIO (m :: Type -> Type)
- type InternalState = IORef ReleaseMap
- getInternalState :: Monad m => ResourceT m InternalState
- runInternalState :: ResourceT m a -> InternalState -> m a
- withInternalState :: (InternalState -> m a) -> ResourceT m a
- createInternalState :: MonadIO m => m InternalState
- closeInternalState :: MonadIO m => InternalState -> m ()
- class Monad m => MonadThrow (m :: Type -> Type) where
Data types
The Resource transformer. This transformer keeps track of all registered
actions, and calls them upon exit (via runResourceT
). Actions may be
registered via register
, or resources may be allocated atomically via
allocate
. allocate
corresponds closely to bracket
.
Releasing may be performed before exit via the release
function. This is a
highly recommended optimization, as it will ensure that scarce resources are
freed early. Note that calling release
will deregister the action, so that
a release action will only ever be called once.
Since 0.3.0
Instances
data ReleaseKey Source #
A lookup key for a specific release action. This value is returned by
register
and allocate
, and is passed to release
.
Since 0.3.0
Unwrap
runResourceT :: MonadUnliftIO m => ResourceT m a -> m a Source #
Unwrap a ResourceT
transformer, and call all registered release actions.
Note that there is some reference counting involved due to resourceForkIO
.
If multiple threads are sharing the same collection of resources, only the
last call to runResourceT
will deallocate the resources.
NOTE Since version 1.2.0, this function will throw a
ResourceCleanupException
if any of the cleanup functions throw an
exception.
Since: 0.3.0
Check cleanup exceptions
runResourceTChecked :: MonadUnliftIO m => ResourceT m a -> m a Source #
Backwards compatible alias for runResourceT
.
Since: 1.1.11
data ResourceCleanupException Source #
Thrown when one or more cleanup functions themselves throw an exception during cleanup.
Since: 1.1.11
ResourceCleanupException | |
|
Instances
Special actions
resourceForkWith :: MonadUnliftIO m => (IO () -> IO a) -> ResourceT m () -> ResourceT m a Source #
Introduce a reference-counting scheme to allow a resource context to be shared by multiple threads. Once the last thread exits, all remaining resources will be released.
The first parameter is a function which will be used to create the
thread, such as forkIO
or async
.
Note that abuse of this function will greatly delay the deallocation of registered resources. This function should be used with care. A general guideline:
If you are allocating a resource that should be shared by multiple threads,
and will be held for a long time, you should allocate it at the beginning of
a new ResourceT
block and then call resourceForkWith
from there.
Since: 1.1.9
resourceForkIO :: MonadUnliftIO m => ResourceT m () -> ResourceT m ThreadId Source #
Launch a new reference counted resource context using forkIO
.
This is defined as resourceForkWith forkIO
.
Note: Using regular forkIO
inside of a ResourceT
is inherently unsafe,
since the forked thread may try access the resources of the parent after they are cleaned up.
When you use resourceForkIO
or resourceForkWith
, ResourceT
is made aware of the new thread, and will only cleanup resources when all threads finish.
Other concurrency mechanisms, like concurrently
or race
, are safe to use.
If you encounter InvalidAccess
exceptions ("The mutable state is being accessed after cleanup"),
use of forkIO
is a possible culprit.
Since: 0.3.0
Monad transformation
transResourceT :: (m a -> n b) -> ResourceT m a -> ResourceT n b Source #
Transform the monad a ResourceT
lives in. This is most often used to
strip or add new transformers to a stack, e.g. to run a ReaderT
.
Note that this function is a slight generalization of hoist
.
Since 0.3.0
joinResourceT :: ResourceT (ResourceT m) a -> ResourceT m a Source #
This function mirrors join
at the transformer level: it will collapse
two levels of ResourceT
into a single ResourceT
.
Since 0.4.6
Registering/releasing
:: MonadResource m | |
=> IO a | allocate |
-> (a -> IO ()) | free resource |
-> m (ReleaseKey, a) |
Perform some allocation, and automatically register a cleanup action.
This is almost identical to calling the allocation and then
register
ing the release action, but this properly handles masking of
asynchronous exceptions.
Since 0.3.0
:: MonadResource m | |
=> IO a | allocate |
-> IO () | free resource |
-> m ReleaseKey |
Perform some allocation where the return value is not required, and automatically register a cleanup action.
allocate_
is to allocate
as bracket_
is to bracket
This is almost identical to calling the allocation and then
register
ing the release action, but this properly handles masking of
asynchronous exceptions.
Since: 1.2.4
register :: MonadResource m => IO () -> m ReleaseKey Source #
Register some action that will be called precisely once, either when
runResourceT
is called, or when the ReleaseKey
is passed to release
.
Since 0.3.0
release :: MonadIO m => ReleaseKey -> m () Source #
Call a release action early, and deregister it from the list of cleanup actions to be performed.
Since 0.3.0
unprotect :: MonadIO m => ReleaseKey -> m (Maybe (IO ())) Source #
Unprotect resource from cleanup actions; this allows you to send resource into another resourcet process and reregister it there. It returns a release action that should be run in order to clean resource or Nothing in case if resource is already freed.
Since 0.4.5
resourceMask :: MonadResource m => ((forall a. ResourceT IO a -> ResourceT IO a) -> ResourceT IO b) -> m b Source #
Perform asynchronous exception masking.
This is more general then Control.Exception.mask
, yet more efficient
than Control.Exception.Lifted.mask
.
Since 0.3.0
Type class/associated types
class MonadIO m => MonadResource m where Source #
A Monad
which allows for safe resource allocation. In theory, any monad
transformer stack which includes a ResourceT
can be an instance of
MonadResource
.
Note: runResourceT
has a requirement for a MonadUnliftIO m
monad,
which allows control operations to be lifted. A MonadResource
does not
have this requirement. This means that transformers such as ContT
can be
an instance of MonadResource
. However, the ContT
wrapper will need to be
unwrapped before calling runResourceT
.
Since 0.3.0
liftResourceT :: ResourceT IO a -> m a Source #
Lift a ResourceT IO
action into the current Monad
.
Since 0.4.0
Instances
type MonadResourceBase = MonadUnliftIO Source #
Deprecated: Use MonadUnliftIO directly instead
Just use MonadUnliftIO
directly now, legacy explanation continues:
A Monad
which can be used as a base for a ResourceT
.
A ResourceT
has some restrictions on its base monad:
runResourceT
requires an instance ofMonadUnliftIO
.MonadResource
requires an instance ofMonadIO
Note that earlier versions of conduit
had a typeclass ResourceIO
. This
fulfills much the same role.
Since 0.3.2
Low-level
data InvalidAccess Source #
Indicates either an error in the library, or misuse of it (e.g., a
ResourceT
's state is accessed after being released).
Since 0.3.0
Instances
Show InvalidAccess Source # | |
Defined in Control.Monad.Trans.Resource.Internal showsPrec :: Int -> InvalidAccess -> ShowS # show :: InvalidAccess -> String # showList :: [InvalidAccess] -> ShowS # | |
Exception InvalidAccess Source # | |
Defined in Control.Monad.Trans.Resource.Internal |
Re-exports
class MonadIO m => MonadUnliftIO (m :: Type -> Type) #
Monads which allow their actions to be run in IO
.
While MonadIO
allows an IO
action to be lifted into another
monad, this class captures the opposite concept: allowing you to
capture the monadic context. Note that, in order to meet the laws
given below, the intuition is that a monad must have no monadic
state, but may have monadic context. This essentially limits
MonadUnliftIO
to ReaderT
and IdentityT
transformers on top of
IO
.
Laws. For any value u
returned by askUnliftIO
, it must meet the
monad transformer laws as reformulated for MonadUnliftIO
:
unliftIO u . return = return
unliftIO u (m >>= f) = unliftIO u m >>= unliftIO u . f
Instances of MonadUnliftIO
must also satisfy the idempotency law:
askUnliftIO >>= \u -> (liftIO . unliftIO u) m = m
This law showcases two properties. First, askUnliftIO
doesn't change
the monadic context, and second, liftIO . unliftIO u
is equivalent to
id
IF called in the same monadic context as askUnliftIO
.
Since: unliftio-core-0.1.0.0
Instances
MonadUnliftIO IO | |
Defined in Control.Monad.IO.Unlift | |
MonadUnliftIO m => MonadUnliftIO (ResourceT m) Source # | Since: 1.1.10 |
Defined in Control.Monad.Trans.Resource.Internal | |
MonadUnliftIO m => MonadUnliftIO (IdentityT m) | |
Defined in Control.Monad.IO.Unlift | |
MonadUnliftIO m => MonadUnliftIO (ReaderT r m) | |
Defined in Control.Monad.IO.Unlift |
Internal state
A ResourceT
internally is a modified ReaderT
monad transformer holding
onto a mutable reference to all of the release actions still remaining to be
performed. If you are building up a custom application monad, it may be more
efficient to embed this ReaderT
functionality directly in your own monad
instead of wrapping around ResourceT
itself. This section provides you the
means of doing so.
type InternalState = IORef ReleaseMap Source #
The internal state held by a ResourceT
transformer.
Since 0.4.6
getInternalState :: Monad m => ResourceT m InternalState Source #
Get the internal state of the current ResourceT
.
Since 0.4.6
runInternalState :: ResourceT m a -> InternalState -> m a Source #
Unwrap a ResourceT
using the given InternalState
.
Since 0.4.6
withInternalState :: (InternalState -> m a) -> ResourceT m a Source #
Run an action in the underlying monad, providing it the InternalState
.
Since 0.4.6
createInternalState :: MonadIO m => m InternalState Source #
Create a new internal state. This state must be closed with
closeInternalState
. It is your responsibility to ensure exception safety.
Caveat emptor!
Since 0.4.9
closeInternalState :: MonadIO m => InternalState -> m () Source #
Close an internal state created by createInternalState
.
Since 0.4.9
Reexport
class Monad m => MonadThrow (m :: Type -> Type) where #
A class for monads in which exceptions may be thrown.
Instances should obey the following law:
throwM e >> x = throwM e
In other words, throwing an exception short-circuits the rest of the monadic computation.
throwM :: Exception e => e -> m a #
Throw an exception. Note that this throws when this action is run in
the monad m
, not when it is applied. It is a generalization of
Control.Exception's throwIO
.
Should satisfy the law:
throwM e >> f = throwM e