The last few weeks I implemented a few syntactic changes in Rust. I wanted to go over those and explain the motivation so it doesn't just seem like churn. None of the designs were mine, but I agree with all of them. (Oh, by the way, did you...
My thoughts on Rust in 2015 Disclaimer: these are my personal thoughts on where I would like to see Rust go in 2015 and what I would like to work on. They are not official policy from the Rust team or anything like that.The obvious big thin...
Rust for C++ programmers - part 7: data types In this post I'll discuss Rust's data types. These are roughly equivalent to classes, structs, and enums in C++. One difference with Rust is that data and behaviour are much more strictly separa...
So far we've covered unique and borrowed pointers. Unique pointers are very similar to the new std::unique_ptr in C++ and borrowed references are the 'default' pointer you usually reach for if you would use a pointer or reference in C++. Ru...
Rust for C++ programmers - part 5: borrowed references In the last post I introduced unique pointers. This time I will talk about another kind of pointer which is much more common in most Rust programs: borrowed pointers (aka borrowed refer...
Rust for C++ programmers - part 4: unique pointers Rust is a systems language and therefore must give you raw access to memory. It does this (as in C++) via pointers. Pointers are one area where Rust and C++ are very different, both in synt...
Rust for C++ programmers - part 9: destructuring pt2 - match and borrowing (Continuing from part 8, destructuring).(Note this was significantly edited as I was wildly wrong the first time around. Thanks to /u/dpx-infinity for pointing out m...