I believe the primary reason why select must be in the language is because it integrates tightly with goroutine scheduling to efficiently block, and then wake up when one of its channel operations can complete.
On Thursday, January 19, 2017 at 12:33:38 PM UTC-5, John C. wrote: > > On several occasions the Go designers have alluded to the fact that the > 'select' mechanism and the fact that it's built in to the language are very > important for concurrency (can't seem to find references). While I > understand just fine how to use select/goroutines/channels, the overarching > importance of select as a built-in feature is escaping me. > > Can somebody help me see the big "why" picture better? > > Thanks, > John C. > > -- 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.
