[go-nuts] Scheduler discrepancy between Linux and OS X with Gosched()

I've run into some mysterious behavior, where Gosched() works as expected in Mac OS X, but only works as expected in Ubuntu if I put a logging statement before it. I originally posted this on Stack Overflow but was directed here. Post: https://stackoverflow.com/questions/49617451/golang-schedul

[go-nuts] Re: Scheduler discrepancy between Linux and OS X with Gosched()

Hi Dave, thanks for the reply! It makes sense that the send c <- 0 is not guaranteed to transfer control to the receiving goroutine. But is it not guaranteed that runtime.Gosched() will at least check if another goroutine is runnable? I thought that was roughly the point of runtime.Gosched().