4 ms·
The code, which would break, was already broken. Just in far worse ways than throwing exceptions: silent memory corruption. And there would be no backwards-comp
by yakubin 6y ago
The code, which would break, was already broken. Just in far worse ways than throwing exceptions: silent memory corruption. And there would be no backwards-compatibility breakage, since in cases, where it would throw, currently UB is triggered.
- andrewprock 6y agoThe existing code may be "broken" but it is making too much money to risk changing it for pedantic reasons.
- Koiwai 6y agoSimply do not compile them using -std=future then.