Changing std:sort at Google’s scale and beyond
Seems like mostly a pointless change and it will break some software. Most developers never read the docs. There is always a question about how much rope you should give the users but in these cases my experience tells me that even if the docs clearly state something users will rely on real world results, not the docs. Especially if the development is test driven or if testing is done mainly with automatic tests. I would expect better decisions from the GO team. This is a poor decision not in line with the promises of GO. What did you have to do to not make a breaking change? Add something new and mark the old obsolete?<p>Damn cool algorithm though.