News for hackers. Stuff that matters.
Re:Go 1.5 max procs default by chc on Thursday May 28, 2015 @04:11PM (#9620830)
How are generics backward-incompatible? They would obviously affect forward compatibility, but what previously valid programs would have to become invalid with the introduction of generics? (Incidentally, as an interesting contrast, this GOMAXPROCS default change will break some existing programs.)
Re:Go 1.5 max procs default by prodigal_erik on Thursday May 28, 2015 @07:19PM (#9621804)
The only way to keep old code working would be to add generics but continue having an awful standard library that never uses them.
Re:Go 1.5 max procs default by knodi on Thursday May 28, 2015 @04:24PM (#9620923)
How will GOMAXPROCS default change break existing programs?
Re:Go 1.5 max procs default by chc on Thursday May 28, 2015 @04:45PM (#9621067)
Per the OP: "Increased parallelism could make bugs in racy programs more likely to cause crashes or other problems. The setting of GOMAXPROCS=1 may have thus far let those bugs go undetected. Raising it may therefore make buggy programs less reliable."
Re:Go 1.5 max procs default by ecnahc515 on Thursday May 28, 2015 @04:37PM (#9621012)
GOMAXPROCS isn't really a language feature, that's all implementation specific AFAIC.