3 ms·
> 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 f
by Filligree 10y ago
> 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.
- knorker 10y ago> There are implicit guarantees on when goroutines are scheduled But there's also explicitly no guarantees on that.
- omginternets 10y agoThis 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.