Why does gcc not have a warning option for &x+k where x is an identifier or result of . or -> operator and k!=0,1 (!=0 if dereferenced)?
That has nothing to do with memory safety; it's just UB and an implementation can make it go away by defining the result.
-
-
The hard UBs to eliminate are data races, use after free, aliasing issues.
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.