News for hackers. Stuff that matters.
Re:A Guide to Porting C/C++ to Rust by steveklabnik on Sunday January 29, 2017 @11:23PM (#13518631)
> Would be great instead to see more examples of how e.g. destructive move in That allows generating better assembly.

One example isn't about the destructive aspect: a move in Rust is always a memcpy. Since there's no move constructors, there's no way to run arbitrary code, so it's always a memcpy. The optimizer can also then elide this copy if it isn't actually needed.

Re:A Guide to Porting C/C++ to Rust by quicknir on Monday January 30, 2017 @12:04PM (#13522874)
Yes that's what I was referring to, the terminology I used has been used before in C++. Rust s moves are considered destructive in the sense that the old object is no longer functional, which of course is fine because it can't be used.
Re:A Guide to Porting C/C++ to Rust by steveklabnik on Monday January 30, 2017 @01:28PM (#13523717)
Oh yeah sorry, I see what you're saying now.