4 ms·
> [...] Go does it implicitly at various key locations. This is actually pretty surprising to many folks, it was in the past and maybe still is possible to dead
by systemcluster 7y ago
> [...] Go does it implicitly at various key locations. This is actually pretty surprising to many folks, it was in the past and maybe still is possible to deadlock Go with a certain incantation of tight looping.
This is being worked on here: https://github.com/golang/go/issues/24543 https://github.com/golang/go/issues/24543
- jchw 7y agoFascinating. This would make Goroutines one giant leap closer to being thread-like. It feels weird how much of the OS scheduler is being “duplicated” but you can’t really argue much with the results.
- tomp 7y agoIs there any documentation on the latest status on this, how far along they've come and what technical solutions they're considering / have settled on?
- jchw 7y agoThe proposal is marked accepted, and commits are being made to reference it, so I suppose the design doc and that issue are most likely the source of truth.