Skip to content

Why does monitor not provide a reply message? #308

Open
@hyperthunk

Description

@hyperthunk

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...

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions