It would help, but it wouldn't get rid of the errors.
It would convert corruption/security bugs into other, much safer runtime errors.
To get rid of the runtime error altogether, we need a stronger type system or a different form of static analysis, as mentioned here.
Also, the extra bounds checking might be somewhat expensive in some scenarios, especially as the fat pointers would consume many more cache lines than thin pointers.
It would convert corruption/security bugs into other, much safer runtime errors.
To get rid of the runtime error altogether, we need a stronger type system or a different form of static analysis, as mentioned here.
Also, the extra bounds checking might be somewhat expensive in some scenarios, especially as the fat pointers would consume many more cache lines than thin pointers.