the blog link is nice, thank you very much. Its long but worth read: `C#’s implementation of async/await is entirely a front-end compiler trick. If you’ve ever run ildasm on the resulting assembly, you know: it lifts captured variables into fields on an object, rewrites the method’s body into a state machine, and uses Task’s continuation passing machinery to keep the iterator-like object advancing through the states.`
Nim´s one is more like in node.js (I think). If you process large chunks at once or a endless loop is placed inside you will break your entire system... And yes, the Nim channel`s impl is "very fat". Thats the reason I did the messaging within my timperpool impl with Locks and Conditions. Basically you can do everything with Locks and Conditions but thats a little bit "low level". So the question could be: whats the audience/usecase for async/await - feature vs threads? new Nim users could be confused about that (like me).
