Re:Don’t assume that safety comes for free: a Swift case study
by mikeash on Thursday December 08, 2016 @09:48AM
(#13130569)
You either have to pick a default, or you have to forbid developers from writing a + operation unless they first choose an overflow behavior. I can see arguments for the latter, but it's not a common choice.
And yet again - this is UB because the original writers of the C language knew that the behavior of the hardware would be known to assembly programmers of the time.