@@ -77,7 +77,7 @@ module Control.Distributed.Process.Internal.Primitives
78 , unmonitor
78 , unmonitor
79 , withMonitor
79 , withMonitor
80− , withMonitorRef
80+ , withMonitor_
81 -- * Logging
81 -- * Logging
83 -- * Registry
83 -- * Registry
@@ -887,21 +887,19 @@ monitor = monitor' . ProcessIdentifier
887-- @withMonitor@ returns, there might still be unreceived monitor
887-- @withMonitor@ returns, there might still be unreceived monitor
888-- messages in the queue.
888-- messages in the queue.
890−withMonitor :: ProcessId -> Process a -> Process a
890+withMonitor :: ProcessId -> (MonitorRef -> Process a) -> Process a
891−withMonitor pid = withMonitorRef pid . const
891+withMonitor pid = bracket (monitor pid) unmonitor
892− -- unmonitor blocks waiting for the response, so there's a possibility
893− -- that an exception might interrupt withMonitor before the unmonitor
894− -- has completed. I think that's better than making the unmonitor
897-- | Establishes temporary monitoring of another process.
893-- | Establishes temporary monitoring of another process.
899−-- @withMonitorRef pid code@ sets up monitoring of @pid@ for the duration
895+-- @withMonitor_ pid code@ sets up monitoring of @pid@ for the duration
900−-- of @code@. Note: although monitoring is no longer active when
896+-- of @code@. Note: although monitoring is no longer active when
901−-- @withMonitorRef@ returns, there might still be unreceived monitor
897+-- @withMonitor_@ returns, there might still be unreceived monitor
902-- messages in the queue.
898-- messages in the queue.
903−withMonitorRef :: ProcessId -> (MonitorRef -> Process a) -> Process a
901+withMonitor_ :: ProcessId -> Process a -> Process a
904−withMonitorRef pid code = bracket (monitor pid) unmonitor code
902+withMonitor_ p = withMonitor p . const
906-- | Remove a link
904-- | Remove a link