> > Thus, they aren't equivalent to GoLang's "green threads" which have the > > injected code necessary to be able to very quickly suspend and resume tiny > > chunks of code, but hopefully that won't be necessary and @araq doesn't > > want to go that route anyway. > > I don't mind it too much and the mechanism could be built into Nim's "goto > based exception" handling implementation...
That's an interesting idea, but I don't know that even with the shortcuts available with "goto based exceptions" that we could get as fast as Go's go routines which seem to be true coroutines. Could be wrong, though :-) > but it's not clear to me if we really need it. It's not clear to me either; I, personally, have never needed it and I suspect that 99.9% of the programmers who have ever called go routines haven't needed their speed. OTOH, being able to `spawn` routines to be run from a CPU core thread backed thread pool is something that is useful, both in terms of ease of use and in terms of performance as compared to the alternative of creating new OS threads, so that's what we should work on first (IMO, of course).
