Re:A Usable C++ Dialect That Is Safe Against Memory Corruption
by fjsolwmv on Thursday March 15, 2018 @06:43PM
(#16597111)
The compiler shouldn't rejected UB, it should define all behavior, and reject all code constructs that can't have behavior fully defined (like accessing raw pointers as arrays, so bounds- checking is impossible). It can throw an exception on null de-reference at runtime. That's slow, but safe.
[ Parent
| on HN ]