There's also the issue that undefined behaviour tends to become
exploitable as part of a security hole.
So I'm seconding Alekx-Daniel on this.
Am 07.06.2017 um 17:48 schrieb Aleks-Daniel Jakimenko-Aleksejev via RT:
(for example, because this kind of stuff
makes the language look fragile).
Let's resolve the issue by adding an error message and not by closing our eyes
on this.
On 2017-06-05 03:19:58, c...@zoffix.com wrote:
FWIW, I rescind all of my previous comments on the matter and now
think no special casing should be done to error out on ³² or anything
like that.
The only people I see complaining about it are those who just type it
up randomly to see what it'd do; i.e. not an issue in real programs. I
see no sufficient argument to add special casing in code,
documentation, and tests, without solving any real problems.
