Re:C-for-all: Extending C with modern safety and productivit...
by fluffything on Wednesday December 04, 2019 @03:49AM
(#21700644)
All memory allocations in Rust follow a `malloc`-like API that ends up calling `malloc` and similar at some point.
Re:C-for-all: Extending C with modern safety and productivit...
by saagarjha on Wednesday December 04, 2019 @03:52AM
(#21700658)
With memory management, the question is often when and how to release resources, not how to get untyped memory from the operating system.
Re:C-for-all: Extending C with modern safety and productivit...
by fluffything on Wednesday December 04, 2019 @05:24PM
(#21707881)
Sure, but in Rust, the programmer writes code that calls malloc manually, which is completely different from Java.
Their key points seem to be that Rust (and other existing languages) lack backwards compatibility and have different memory management strategies. Lumping Rust in with GC languages is confusing.
Whether either of those things matter is another story. From using TypeScript, I'm personally inclined to believe that a superset of a difficult language can't solve all of the underlying problems, while a totally new language can.