The idea behind Zig approach which is only being implemented is to extend concurrent code to be executable outside the coroutine context, making it trivially se

The idea behind Zig approach which is only being implemented is to extend concurrent code to be executable outside the coroutine context, making it trivially serializable when that's possible (thus the networking example). In general, the heavy lifting should always be moved to the lower level infrastructure (compiler, standard library, RDBMS system in case of ACID guarantees...) — leaving developer his brainspace for the business logic. This requires minimum "function coloring", and I'd prefer if Python took that approach instead.