A 30-minute Introduction to Rust
doc.rust-lang.org
A 30-minute Introduction to Rust
1–10 of 94 posts
Re: A 30-minute Introduction to Rust
#2I wrote this a while back as a blog post, it ended up being the actual intro. I hope to go over it again soon, and make it better. There's nothing super wrong with it, but you can always improve! Feedback welcome.
Oh, and we had a big discussion last time: https://news.ycombinator.com/item?id=7051835
Re: A 30-minute Introduction to Rust
#3I wrote this a while back as a blog post, it ended up being the actual intro. I hope to go over it again soon, and make it better. There's nothing super wrong with it, but you can always improve! Feedback welcome. Oh, and we had a big discussion last time: https://news.ycombinator.com/item?id=7051835
I knew this was your work!
EDIT:
concurrency.rs:12:20: 12:27 error: use of moved value: 'numbers'
Re: A 30-minute Introduction to Rust
#4I wrote this a while back as a blog post, it ended up being the actual intro. I hope to go over it again soon, and make it better. There's nothing super wrong with it, but you can always improve! Feedback welcome. Oh, and we had a big discussion last time: https://news.ycombinator.com/item?id=7051835
I knew this was your work! EDIT: concurrency.rs:12:20: 12:27 error: use of moved value: 'numbers' Is this a compile-time or a run-time error?
Compile-time.
Re: A 30-minute Introduction to Rust
#5I gotta say, reading this actually made me really excited about Rust. C++ without the annoying memory management but no GC-overhead sounds like a dream.
Re: A 30-minute Introduction to Rust
#6Is the language stable enough to learn yet (given that I won't be really using it immediately)? I've been putting off looking at it because it seemed very much in flux.
Re: A 30-minute Introduction to Rust
#7[deleted]
Re: A 30-minute Introduction to Rust
#8I gotta say, reading this actually made me really excited about Rust. C++ without the annoying memory management but no GC-overhead sounds like a dream.
Just to temper your enthusiasm, the compiler errors can sometimes be irritating, especially when you want to do something the you are pretty sure will be safe. But on the whole if you work with it the pay-off is well worth the minor annoyances. Having the compiler always check your code for memory safety is a huge win for refactoring - C or C++ code bases get really brittle over time as developers forget what is actually going on. I would also say that the number of errors you encounter over time reduce as you gain an intuition for the rules.
Re: A 30-minute Introduction to Rust
#9Is the language stable enough to learn yet (given that I won't be really using it immediately)? I've been putting off looking at it because it seemed very much in flux.
For learning I would say it is. The biggest thing at the moment is API changes. But the team is now pushing to put stability attributes on all modules and marking deprecated items as such for a time before their removal (these emit warnings if used).
I would highly recommend using the nightlies from http://rust-lang.org/. A list of the docs can be found here: http://doc.rust-lang.org/index.html Reddit is also good for keeping up to date on news: http://www.reddit.com/r/rust Also, IRC is your friend! Join #rust at irc.mozilla.org, and feel free to ask questions. The community is very friendly and willing to help.
Re: A 30-minute Introduction to Rust
#10I gotta say, reading this actually made me really excited about Rust. C++ without the annoying memory management but no GC-overhead sounds like a dream.
Just to temper your enthusiasm, the compiler errors can sometimes be irritating, especially when you want to do something the you are pretty sure will be safe. But on the whole if you work with it the pay-off is well worth the minor annoyances. Having the compiler always check your code for memory safety is a huge win for refactoring - C or C++ code bases get really brittle over time as developers forget what is actu…
> especially when you want to do something the you are pretty sure will be safe
(It's worth noting that often the compiler is complaining because it actually isn't safe.)