Tim Watson

And of course, it'd be _really_ nice if we came up with a way to do "distributed finalization", but that's really beyond the scope of this ticket. :)

> It may be worth keeping the code from the related ToChildStart instances in d-p-p but as plain functions and in a separate module accompanied by documentation and warnings specific...

> Does that sound ok to you? If so, I'll open a new PR for each. Yeah that sounds good to me. Thanks for all the work you've been putting...

So.... where are we with _this_ pull request now @tavisrudd ?

I'm going to have to release without this fix I'm afraid, as I'm on holiday next week and this is the last chance I'm going to have to actually make...

Caveats - unless you can get me a fix in the next few hours.... :) ?

Hey @tavisrudd - how're you? Do you want me to pick up the fix for this?

Ok @tavisrudd - I'm going to pick this one up now. As you can tell, I've been a bit on the busy side myself!

> And here for RabbitMQ's server code base (distinct tags: 'DOWN', nodeup, new_pg2_fixed, 'EXIT', bump_credit, mnesia_system_event, delayed_restart, and inet_async): In RabbitMQ, like most erlang code bases we use 'EXIT" and...

> In RabbitMQ, like most erlang code bases we use 'EXIT" and 'DOWN' extensively. Cloud Haskell doesn't appear to support 'EXIT' signals in the same way erlang does I'd better...