> I quite like it and don't see any particular problem or traps with it. While Go's model is certainly a valid point in the design space and keeps things nice

> I quite like it and don't see any particular problem or traps with it. While Go's model is certainly a valid point in the design space and keeps things nice and simple, there are of course going to be many trade-offs. For example, low-level control is very much lost. There are no opportunities for custom schedulers, optimising how non-blocking calls are made, or easily dealing with blocking syscalls (or foreign libraries that call them). It would not be the right approach for Rust.