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.
[ Parent
| on HN ]
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?