Can't we just enable bounds checking and gc and live with slowness. Shouldn't that be a choice, a compiler flag ?
Every time there is a security issue, someone can see your naked pictures.
Every time there is a security issue, someone can see your naked pictures.
GC is one way to reduce the number of memory safety issues, but there are often tricky interactions between GC and non-GC code. Another issue with GC is it's often much harder to reason about object lifetimes.