>This seems like a "can implement, but not very cleanly" case, which would be a great justification for a library, but not a language feature. First sentence o

>This seems like a "can implement, but not very cleanly" case, which would be a great justification for a library, but not a language feature. First sentence of OP: > This post is about why we need a coroutine package for Go Then in the girst section after the intro: > Later, I will argue for an optimized implementation provided directly by the runtime, but that implementation should be indistinguishable from the pure Go definition.