And it didn't need to be broken. E.g. if Clang had -fno-strict-aliasing set by default, it would still be a conforming impl.
You missed the point. Defining most UB requires determining when it happens, which requires very expensive tracking.
-
-
Or the code is written in such a way that it can absorb whatever naturally happens on the platform (without a check).
-
"Whatever naturally happens" cannot be defined consistently when you have out-of-bounds pointer arithmetic, etc.
-
One usually does not need to worry about supporting an infinite number of unknown platforms.
-
Like, some of us just do x86_64 posix & windows, and it's fine.
-
And even those that *do* support a relatively wide variety of hardware (e.g. game engine programmers) are fine with it.
-
Like, it's just another platform layer. It's not as big a deal as you seem to think.
-
Again, I refer you to the post by Jeff Roberts above.
-
In the case of OOB pointers, yeah, you either get a segfault or possibly garbage. That's bad, and the programmer should fix \
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.