We aren't doing much syntax fiddling and redesigning anymore. 1.0, which is very soon, will have a stability promise and will be backwards compatible.
You can browse around that repository for many other guidelines designed to enforce predictable, coherent choices.
It has been rather ad-hoc for some time now, but we have some great things that are currently landing that will clean tons of this stuff up. Mozilla employee Aaron Turon has been doing a ton of great work shepherding our libraries to a far more polished state. 1.0 is gonna be great!
For example: http://www.reddit.com/r/rust/comments/2kvssl/collections_ref...
I don't even mean it insultingly, there's nothing wrong with instability. I'm a big Perl 6 fan too.
The reason for using nightlies currently is that there is no stability guarantees over the releases (sometimes, your code broke just 2 days after release). So, release doesn't give you benefits, and you are learning an unreleased language, so nightly is the way to go.
I'm pretty sure a lot of libraries will move to stable once there is something that can have the name.
It's a shame there are so many comparisons between Go and Rust because it does both a disservice. Rust is still very much unfinished and still being developed, but despite this it is achieving its goals of complete safety and compile time checking.
It's an admirable project, but it's got a lot of syntax fiddling and redesigning to go before I think it's 'prime time' ready.