Joshua Oreman

Thank you for cleaning this up! Note we now have some uncovered lines for features that were only being exercised on 3.6. I think it would make the most sense...

I've also updated the branch protection rules so that this is now mergeable.

BroadcastValue is an excellent interface IMO. It could be built pretty easily on top of the "channel that drops the oldest enqueued message when a new one arrives" primitive described...

This currently exists (without the "auto cancel when nested child is done" semantics) as `tricycle.open_service_nursery()` (implementation is effectively unchanged from the linked strawman one). I use it all the time....

> I think once services are cancelled, we would consider the nursery closed to new tasks (regardless of whether they're service tasks or regular tasks). Great, that sounds good to...

Hmm. I was imagining "concurrently" but your point about system tasks in #1554 is well taken. - We could cancel in strict reverse order of spawning. That's kinda weird because...

I just realized there is actually an escape hatch if the default is "cancel in reverse spawning order" and you really want multiple service tasks to be cancelled at the...

> I'd like to understand the use cases a bit better, for when you'd use this versus regular guest mode. With regular guest mode, the Trio run is nested entirely...

I think you could support `attr.slots()` in the class body using the trace hook: ``` In [35]: def slottify(frame, old_trace): ...: old_local_trace = [frame.f_trace] ...: def tracer(frame, event, arg): ...:...

I think maybe a useful question here is, when are limitations that exist only on some interpreters worse than limitations that exist on all interpreters? (This isn't intended to be...