2 ms·
> For one, the heap is reference counted - and if you use std::gc its... mark/sweep(not sure?). No, the heap primarily uses unique ownership, which is equivale
by pcwalton 13y ago
> For one, the heap is reference counted - and if you use std::gc its... mark/sweep(not sure?).
No, the heap primarily uses unique ownership, which is equivalent to malloc/free. Reference counting is an option (and mark/sweep in the future) but idiomatic Rust only uses reference counting where it is necessary.
> Secondly from my initial use of Rust I dont think you cannot protect a chunk of data with a lock and share it (w/o copying) across threads/processes as you would with a systems language like C++.
Yes, you can. http://static.rust-lang.org/doc/master/extra/arc/struct.MutexArc.html http://static.rust-lang.org/doc/master/extra/arc/struct.Mute...
> Rust is not aimed at high performance applications - I dont see anything wrong with that statement.
Rust is aimed at high performance applications and has been since day one.
- ksk 13y agoSo are you confirming or denying that Rust is about zero-cost abstraction? Because it sounds like you're saying if you don't use any abstractions, its zero cost :) Anyway, I don't have anything against Rust. I cheer for their success.