News for hackers. Stuff that matters.
Re:Cmd/compile: Go 1.8 regression: sync/atomic loop elided by Filligree on Monday February 20, 2017 @10:20AM (#13687949)
> Because sync.Wait() isn't used, there's no guarantee the goroutine will execute at all before program halt.

This is the sort of reasoning I'd expect to see from C apologists. Go should be better...

There are implicit guarantees on when goroutines are scheduled, too. The scheduler makes some attempts at fairly spreading the CPU.

Re:Cmd/compile: Go 1.8 regression: sync/atomic loop elided by knorker on Monday February 20, 2017 @12:28PM (#13689086)
> There are implicit guarantees on when goroutines are scheduled

But there's also explicitly no guarantees on that.

Re:Cmd/compile: Go 1.8 regression: sync/atomic loop elided by omginternets on Monday February 20, 2017 @07:14PM (#13692168)
This is unfair, I think. Go offers strong guarantees that C does not. It has fewer sharp edges than C; it also asserts a principle of not polishing away sharp edges with concurrency.

You don't have to do everything better than C to be a huge improvement over C.