@spun_off so I was thinking about the benefits of UB for bug indication and concluded there is none
Checking for OOB accesses, aliasing errors, double free, etc. with full accuracy is NOT easy or cheap.
-
-
you can permit BOTH.
-
UB _is_ the formal model for permitting both. Are you just objecting to the name "UB"?
-
nope. UB permits *more* than these two. I want to permit *exactly* these two.
-
an implementation can *either* define the behavior to [something sensible] *or* make it a trap while being conformant.
-
NB: I don't think there's a snowball's chance in hell WG14 actually adopts this. I am saying that UB is not strictly…
-
necessary to find bugs in this way, just like -Werror diagnoses constructs that aren't (necessarily) invoking UB
End of conversation
New conversation -
-
-
for integer overflow at least, Rust might have arrived at a good set of tradeoffs http://huonw.github.io/blog/2016/04/myths-and-legends-about-integer-overflow-in-rust/ …
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
fact is, Ada does not have nearly as much UB as C does, and is still hellish fast, at least O(C)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.