John Belmonte

I have no doubt that multi-channel, 16-bit sound can be handled well within fixed-point, 32-bit operations. (The PlayStation or early consoles and sound cards had no floating point hardware, etc.)...

> Would there be interest in adding a variant of wait that only returns if the predicate is still True? It isn't possible to implement, based on the way coroutines...

> ... now we know that "foo" is bar, at least until we do something that yields control I'd argue that this is an uphill battle, because in general code...

That's correct. I see, so the wait function is checking the value, and either returning directly to the caller or going back to sleep. Along the lines of my other...

There was some discussion of this on a Trio issue, https://github.com/python-trio/trio/issues/1089#issuecomment-521552829, and that thread noted the obstacle that a generator can't yield from an internal nursery. So you end up...

I think the body of `as_completed()` itself needs a `yield` to be a generator. The `yield` in `yield_result()` applies to that nested function (making it an async generator), rather than...

I guess the function results feed into a trio memory channel, and the main loop just yields incoming items?

breaking changes in upcoming release trio-util 0.5.0: - `compose_values()` context manager was changed from async to synchronous - `RepeatedEvent` replaces both `UnqueuedRepeatedEvent` and `MailboxRepeatedEvent`

Happy to consider them. Is the implementation in a public repo already by any chance? I don't have a sense for how general of a need these fill.

> that early exit on line 84 is wrong btw... it won't notice the Cancelled in MultiError([RuntimeError, MultiError([Cancelled, Cancelled])]) fixed in 58db781 > those raise statements will automatically attach the...