I have seen a lot of confusion on how go routines actually work internally. Will the function execution ontop of the go routine be rewritten to a statemachine with continuations in the same way as the C# async await does?
If I have only 1 OS thread and 1000 go routines, obviously there must be some sort of "magic" that makes it possible to multiplex these ontop of that thread. How do the go routines store state so that they can continue from the last execution point when they resume execution? Is it safe to say that Go gives you the exact same support as the C# (and others) async await while still writing code that looks sequential? -- 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.
