Tim Watson

> I would say ideally logging is independent of the backend. That's my opinion too. Unless @dcoutts and/or @simonmar have major objections then, I suggest we go ahead with this...

> We have a few weeks before the book is due to be ready, so you have until then to decide on the API :) He he he - ok...

So, I've come to the conclusion that `say` should remain, as I think any _logging infrastructure_ that does get built up will reside in d-p-platform. We should have _some_ kind...

So would we store the accepted mailbox as Map Fingerprint (StrictList a) or some such? Is Map the right data structure for this or donee want a strict version?

> You have to be very careful here: you still need to guarantee ordering. Yes of course, I was jumping ahead without thinking there. I suspect then, some kind of...

+1

I've deleted my comments/questions about the branching process. We can discuss it on the mailing list instead. @qnikst that deprecation message looks fine to me.

I'm going to pull together a fix for the tracing bugs and a hope to close out a number of other open issues, so let's sit tight until I've got...

I'll do it once the rest of my patches have been merged.

I don't think we need to do anything special here. I suppose we could associate process identifiers with thread ids, but most of what Threadscope does will just work, as...