Tim Watson

@mboes you're right, I don't think `unmonitor\1` is useful unless the calling process is trying to exit quickly. In that case however, it might've made sense at one time to...

Yes okay @mboes, I can't really disagree that we shouldn't choose semantics based on implementation details. And stray monitor signals _are_ a pain, so let's merge #252 then, and address...

Erlang supports both kinds of tracing. The one @gbaz mentioned based on lamport clocks is http://www.erlang.org/doc/man/seq_trace.html, whereas the dynamic process tracing I mentioned is a separate, complimentary feature built into...

> It would also be useful to add metrics such as message queue size (possibly which types). Yes that would be nice. I'm going to split it out into a...

There are some good ideas in this thread, so I'm going to change the title and move it to => Question, viz distributed tracing and hooks into the runtime.

> it is interruptible when no message matches (can it be interrupted even if some message matches?). Yes, and we need to point out that if it is interrupted even...

Folks - I've assigned haskell-distributed org members to this discussion. I know you're all rather busy people, so please excuse the interruption. I'd be delighted to hear your thoughts and...

Yes, thank you @marcozocca-seal - I'm very keen indeed to hear from Adjoint and @tdietert !!

I've posted some discussion to the wiki around [separating actors and channels](https://github.com/haskell-distributed/distributed-process/wiki/Separating-Channels-and-Actors)

Thank you both! > There are still many questions about how to implement concrete steps Yeah, definitely. I'm literally dreaming out loud in the initial post! > I think it...