|
|
|
|
|
|
by touisteur
500 days ago
|
|
|
Haven't seen uncheched_deallocation in modern codebases in a long time... The secondary stack removes many/most use cases of short-lived dynamic allocation and pointer-passing. Controlled types, containers, alleviate most other use-cases. I'd frown at code review if I saw raw memory allocation. Memory safety issues I've seen (very rarely in 15 years of dev) hinge on aliasing, stack overflow (which you can mostly catch now) and tumbling down in C bindings. I'll praise the language I use daily as far more memory-safe than the others I use daily (bar managed-memory Java-like languages). |
|
|