Congrats, you encountered my first complaint with Rust. Let me know how much fun the out-of-date documentation referencing syntax that no longer exists is.
If you ask about it or seek a redress you'll be told, "we're not reeeaaaaaady".
It's a state of affairs they've come to be quite comfortable with.
You're supposed to use Rust unless you're a Mozilla employee or intern, afaict.
I'm following the development of Rust with much interest. The design seems well-thought out, and occasional comments here by 'pcwalton, usually along the lines of “here's how we're trying to solve this problem in Rust”, are always worth a read. I wouldn't start a project in it, however, for at least another year unless my main goal was to experiment with the language.
When I did play with it a little, I indeed ran into problems with out-of-date documentation, but someone in #rust IRC (I think it was 'brson) very helpfully answered my questions and pointed me to some newer docs.
Perhaps your expectations are unrealistic. If you want a language you can use today for a real project, try Clojure or Go. I don't think you can fault the Rust project for being where they are now and communicating honestly.
Maybe you just shouldn't use it now when it's not ready.
There is no reason to complain about missing documentation or other stuff if they didn't get to do it until now. That what "not ready" means. Keep calm and wait ;-)
If you ask about it or seek a redress you'll be told, "we're not reeeaaaaaady".
It's a state of affairs they've come to be quite comfortable with.
You're supposed to use Rust unless you're a Mozilla employee or intern, afaict.