Re:Rust 1.1 Stable, the Community Subteam, and RustCamp
by Gankro on Friday June 26, 2015 @02:49AM
(#9782795)
All destructors in Rust are also decided at runtime, fwiw. Even without any allocation or anything:
let foo = Moves::new();
if condition { mem::drop(foo) }
// should foo be dropped here?
In practice many destructors can probably be scheduled statically at compile time.
Re:Rust 1.1 Stable, the Community Subteam, and RustCamp
by Manishearth on Friday June 26, 2015 @03:15AM
(#9782845)
Dynamic drop is something that will go away for all but the strange deferred-let case (It's not a language restriction). So that's okay.
Rust provides dynamic memory management too, but you aren't forced to use it and most use it for a few variables only.
So far nothing I've seen about Swift tells me that it will be able to be used for things like Servo and other perf-critical applications. Yes, it might edge out Rust webdev, but not much more.
"You cam get a job in swift" is largely due to its iOS backing. I'm not so sure how that's going to apply to other OSs especially if Cocoa and co aren't made open source.