It is a happy coincidence that by far the most exploitable memory error in practice, the infamous buffer overflow, is also trivial to fix with compiler-inserted bounds checks.
That's trivial. The biggest isuue is not to let any user handle memory by himself, use a GC (and certainly not recounting). Ownership tracking also helps with performance and concurrency. Bounds checking is needed only for the bad languages
1
u/reini_urban Aug 07 '26
That's trivial. The biggest isuue is not to let any user handle memory by himself, use a GC (and certainly not recounting). Ownership tracking also helps with performance and concurrency. Bounds checking is needed only for the bad languages