[billjings]

> I'm confused about why we're comparing GOTO control flow with channels, since they're completely unrelated. I guess you can make a mess with each when you use them inappropriately? With GOTO, you should avoid it because there are better options (notably, conditional statements).

Notes On Structured Concurrency goes into some depth on this comparison:

https://vorpus.org/blog/notes-on-structured-concurrency-or-g...

If channel sends are being used as invocations, then this description can apply just as well to channels as it does to the go statement.

[throwaway894345]

> Notes On Structured Concurrency goes into some depth on this comparison:

Yeah, this is why we use `sync.WaitGroup`s and similar abstractions in Go. Using bare channels (like using `goto`) is fine for small local things, but if you're building abstractions you should use patterns like those discussed in the article (for example: https://go.dev/play/p/UoB8ECDbaTw --I'm sure this can be abstracted further).