Matthias Urlichs

> Would users expect that high-precision setting to be inherited by the child task, or not? As a user I would either set up that context inside the task (if...

``` trio.from_thread.async_cm(...) trio.in_thread.run_sync(...) ``` The opposite of "from" is "to", so `to_thread.*` would work for me. `in_thread` is confusing because I read that as "I'm supposed to call these in...

Personally I'm all for copying the context. It's a different environment, after all, and I won't expect anything (besides the return value / exception) to implicitly pass back to the...

If you want to catch exceptions,`outcome` is your friend. In any case, the point of Structured Concurrency is, well, structure. Trio doesn't have the (somewhat-unstructured) interface of `asyncio` precisely because...

Sure, if all you need is a list of results, then go ahead and use the `gather` function from this issue's first answer. That's reasonably simple and probably should be...

Yeah, well, we don't have those syntactic features, and the merits of the Swift syntax are in the eyes of the beholder. If you want a result stream rather than...

There are sufficiently many serial ports (e.g. embedded consoles, `/dev/ttyACM*`) or "ports" (like `/dev/pts`) that can't be talked to with generic USB-serial commands. So why would you want to re-implement...

Huh. That's a big "cannot ever happen" as Trio never sends `None` into a coroutine. So at first glance this looks like a Nuitka bug.

> I don't see any way to define a custom type checking rule. We may not need a custom type checker; as soon as the Awaitable is processed further it'll...

> I don't really dabble in low level stuff, but doesn't the OS / Kernel keep state anyway? Is that not accessible from Python? Yes, it is. The problem is...