Re:How to speed up the Rust compiler in 2018
by dozzie on Monday April 30, 2018 @12:24PM
(#16959905)
Indeed Ada has different memory management model, though equally safe.
[ Parent
| on HN ]
Re:How to speed up the Rust compiler in 2018
by monocasa on Monday April 30, 2018 @12:41PM
(#16960089)
I've coded in Ada. Storage pools are not as safe as Rust's affine type system. For one it's a lot easier to leak memory with Ada, since they're mainly built off of reference counting.
Re:How to speed up the Rust compiler in 2018
by moosingin3space on Monday April 30, 2018 @03:57PM
(#16961708)
Pedantic: memory leaks are memory-safe, despite generally being undesirable.
Re:How to speed up the Rust compiler in 2018
by monocasa on Monday April 30, 2018 @05:15PM
(#16962429)
You're totally right, but yeah, I tend to roll it in to the same category since I consider the denial of service associated with memory leaks to be as bad as stricter memory unsafety. (And to be very pedantic I said 'memory management safety', not just 'memory safety').
Re:How to speed up the Rust compiler in 2018
by pcwalton on Monday April 30, 2018 @05:23PM
(#16962512)
Ada uses a garbage collector for the free store (or just uses unsafe code if it's disabled). Ada's memory management model is not really different from any other typical language.
This is the first time I've ever heard of Ada being garbage collected. Neither
ARM, Barnes' nor Ben-Ari's books, nor GNAT manual say that there is supposed
to be a garbage collector (quite the contrary, the books say that GC is
allowed, but usually not present).
Where did you get your information from?