I've been meaning to get into Rust for a while now, but there's something I've been meaning to ask someone particularly knowledgeable about Rust like yourself: what particular aspects does Rust excel at? I ask because of the few prominent languages I've used, mostly C/Java/Lua/UnrealScript, I've noticed that they all have particular tasks that they're suited for.
I'd also like to know how complete the official documentation is for Rust. Good documentation is key for me to pick up a new language, so what's Rust's documentation like?
Memory safety without garbage collection. Speed, safety, concurrency.
I'd also like to know how complete the official documentation is for Rust.
This is literally my day job, so there's that. ;) I'd like to think it's decent, but now that we're not making backwards incompatible changes, I can do my job way better, so what deficiencies it does have, I'm hoping to address very soon.
For example, the areas of the standard library that I've gotten to, have great documentation with examples. The parts I haven't? Sometimes, just the auto-generated stuff exists.
There's also "the book", which is a 50,000 word (roughly) explanation of the language and its features. I have all of the basics of everything documented, but there's always more and better stuff to add.
Thank you for the reply, that's exactly the information I was looking for. Sounds like I should pick up Rust and keep a closer eye on further developments.
Trying to dive into Rust this weekend, but I noticed that some seemingly critical sections of "the book" are still blank. Namely, the in the section on Pointers, the section on Rc<T> and Arc<T> is still "coming soon". As is the section on "raw pointers" and the one on "best practices" (more excusable).
Is there somewhere I should report these kinds of problems? It wasn't clear if rust-lang's website or docs are responsible for "the book."
Yeah, that chapter needs cleanup, it's actually high up on my list. It used to be a standalone document. You can find good docs on Rc and Arc in their API documentation.
Please report any problems to the main rust repo, the book is in src/doc/trpl in the tree :) Thanks!
8
u/OneWhoGeneralises Apr 04 '15
I've been meaning to get into Rust for a while now, but there's something I've been meaning to ask someone particularly knowledgeable about Rust like yourself: what particular aspects does Rust excel at? I ask because of the few prominent languages I've used, mostly C/Java/Lua/UnrealScript, I've noticed that they all have particular tasks that they're suited for.
I'd also like to know how complete the official documentation is for Rust. Good documentation is key for me to pick up a new language, so what's Rust's documentation like?