News for hackers. Stuff that matters.

A comment on Proposal: Non-cooperative goroutine preemption. Parent comment

Re:Proposal: Non-cooperative goroutine preemption by ngrilly on Thursday March 29, 2018 @10:56AM (#16707558)
> In the simplest form, you do not give up control unless you use I/O, a synchronization primitive, or explicitly give up control (runtime.Gosched() in Go).

This is not how Go works nowadays. There are other preemption points.

[ Parent | on HN ]
Re:Proposal: Non-cooperative goroutine preemption by arghwhat on Thursday March 29, 2018 @11:21AM (#16707758)
That's why I said "in the simplest form".
[ Parent | on HN ]
Re:Proposal: Non-cooperative goroutine preemption by ngrilly on Thursday March 29, 2018 @11:32AM (#16707861)
Yes, but it completely ruins the argument about "it's easy to reason about" ;-)
[ Parent | on HN ]