Here's a timely example of the behavior I'm referring to: https://github.com/websnarf/bstrlib/issues/8 https://github.com/websnarf/bstrlib/issues/8 I'd be happ

Here's a timely example of the behavior I'm referring to: https://github.com/websnarf/bstrlib/issues/8 https://github.com/websnarf/bstrlib/issues/8 I'd be happy to concede that this is not good programming practice, but I do not accept that the compiler is doing us a favor by silently creating this security problem. I do appreciate that gcc at least offers a warning for some of these cases.