Non-local returns are not about anything with concurrency or threads. It is about return from a closure where the thread of execution jumps out of the closure and out of the function that calls it. See this article <https://stackoverflow.com/questions/17663586/non-local-vs-local-returns-matter-of-implementation-level> that explains it well.
Am Freitag, 8. März 2019 14:34:13 UTC+1 schrieb Robert Engels: > > The reason it is hard to do is that Go correctly decided against this > callback type code - it creates callback hell. Concurrency is cheap in Go, > it is designed to use CSP or blocking procedural techniques - both far > easier to maintain than callback focused systems. > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
