You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I do realise this isn't covered by the semantics, but if we reply to the caller with DidUnmonitor, why on earth can't we do it for monitor too? The number of races I've hit up against by calling mRef <- monitor pid; doSomeWorkExpectingMonitorSignalsIfItFails pid mRef is astounding. And documenting this as not guaranteed is fine, but it's a nuisance not having it at all. I realise we can't guarantee anything other than we'll signal you once monitor returns, but still...
The text was updated successfully, but these errors were encountered:
I do realise this isn't covered by the semantics, but if we reply to the caller with
DidUnmonitor
, why on earth can't we do it formonitor
too? The number of races I've hit up against by callingmRef <- monitor pid; doSomeWorkExpectingMonitorSignalsIfItFails pid mRef
is astounding. And documenting this as not guaranteed is fine, but it's a nuisance not having it at all. I realise we can't guarantee anything other than we'll signal you oncemonitor
returns, but still...The text was updated successfully, but these errors were encountered: