Matthias Urlichs

> > The backpressure-on-the-fastest-receiver idea is interesting. But why would you need unbounded buffer space? > > If the slowest receiver is N messages behind the fastest receiver, then you...

I use a version of `ValueEvent` that's specifically not about broadcasting, but about passing exactly one value from one task to exactly one other task. Typical uses are passing a...

Simple solution to the message flag problem: teach the sender to attach a sequence number to each message. I'd rather not over-engineer this. A broadcast on UDP is a lossy...

You can write a combination event-plus-value object easily enough. There are multiple implementations of `ValueEvent` out there. The problems are elsewhere: what do you do when the task that is...

Support? "Substrate" or "Foundation" (because the rest of the code requires its tasks to be there) might work too if we're talking about the nursery itself, but if we assign...

I wonder whether we shouldn't think larger than this. A nontrivial "large" program consists of a bunch of building blocks which depend on each other. This relationship is not linear...

Is there an actual reason for such a check? I mean, adding this check just for the sake of having it just slows down correct programs, while incorrect ones tend...

Mmh. I never do that, I always use either an asynccontextmanager or an asyncexitstack. That stuff is far too easy to get wrong even when only one task is involved.

Is anybody interested in doing the work? I seem to need it and would contribute some $$$ to the effort.

No, the issuer+label texts are scrolling by just fine.