Re:Building native macOS applications with Rust
by pavlov on Wednesday November 30, 2016 @10:49AM
(#13071647)
Rust doesn't have manual memory management -- it just requires you to be very explicit so that the compiler can manage memory for you ;)
[ Parent
| on HN ]
Re:Building native macOS applications with Rust
by amelius on Wednesday November 30, 2016 @11:08AM
(#13071840)
Being very explicit is what I call manual :)
Re:Building native macOS applications with Rust
by kbenson on Wednesday November 30, 2016 @12:08PM
(#13072461)
I would say there's still a pretty big difference between using malloc to allocate space for an array of structs which you have to remember to free later and letting variable definitions and scopes handle that for you, like in many managed languages.
Re:Building native macOS applications with Rust
by digikata on Wednesday November 30, 2016 @12:17PM
(#13072555)
I would call memory in Rust manually managed, but automatically accounted. Vs C which would be both manually managed and accounted.
Re:Building native macOS applications with Rust
by kaoD on Wednesday November 30, 2016 @01:10PM
(#13073075)
I'd say the other way around: Rust is manually accounted (you have to take it into consideration when coding) while the compiler automatically manages it for you.
Re:Building native macOS applications with Rust
by digikata on Wednesday November 30, 2016 @01:28PM
(#13073265)
I think we agree on the fundamental concept, but have a varying way of how one interprets the 'accounting' term: is it the tracking of the memory in various categories (which I think we agree that Rust does automatically in a way that few other languages do), or is it marking of given chunk of memory to be tracked in a certain categoric way (which is what the Rust programmer decides in code). Is there a less ambiguous set of terms to apply for these cases?