Agreed. Besides the language/compiler support, there is a significant library component as well. But without the language/compiler component there is no way to write the library.
-Neal On Jul 13, 2010, at 8:56 AM, Dibyendu Majumdar <[email protected]> wrote: > > > On Jul 13, 1:40 am, Neal Gafter <[email protected]> wrote: >> If you can't do the equivalent of creating hundreds of thousands of >> goroutines that communicate and synchronize among themselves, then you I >> don't think you've captured the spirit of Go. That's hard to do without >> either segmented stacks or compiler-supported coroutines. > > Hi Neal, > > I think it requires more than compiler support or segmented stacks. > Go uses cooperative scheduling between goroutines. > It also wraps around system calls to prevent goroutines from being > blocked. > Much of the synchronisation in Go has to go through the cooperative > scheduler. > > Regards > > -- > You received this message because you are subscribed to the Google Groups > "JVM Languages" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/jvm-languages?hl=en. > -- You received this message because you are subscribed to the Google Groups "JVM Languages" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jvm-languages?hl=en.
