haskell-distributed / haskell-distributed/distributed-process
Why does monitor not provide a reply message?
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 751
- Forks
- 99
- Avg merge
- 45m
- Merged PRs (30d)
- 2
Description
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...
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the monitor and DidUnmonitor semantics mentioned in the issue and tracing how monitor replies are currently handled. Determine whether the requested reply behavior is an implementation change or a documentation clarification; done requires an agreed API outcome that addresses the reported race concerns.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100