On Tue, May 15, 2018 at 5:11 AM, <prab...@qburst.com> wrote: > > Got to read a book about concurrency in go by Katherine cox-Buday, o'Reilly > publications. it says that "Go’s work- > stealing algorithm enqueues and steals continuations" . Is it how work > stealing algorithm works?
It's approximately how Go's work-stealing algorithm works, yes. We don't usually describe goroutines as continuations, but they could reasonably be described that way. Work stealing just means that you have different processors, each with their own queue of things to do, and when one processor's queue is empty it looks in another processor's queue and "steals" what it finds there. Ian -- 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.
