Coroutines for Go

Re:Coroutines for Go by hgsgm on Monday July 17, 2023 @09:50PM (#36766765)

>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.

[ Parent | on HN ]

Re:Coroutines for Go by marcus_holmes on Tuesday July 18, 2023 @12:09AM (#36767697)

Yeah, so I'm agreeing that this would be a great library, but disagreeing that it should be a language feature. Sorry if I didn't make that clear.

[ Parent | on HN ]