X-Git-Url: https://git.ralfj.de/rust-101.git/blobdiff_plain/1a691352b57b7338388ff568403495ecb44272eb..8bfc2246138b487afeb99d9d3161951beda75910:/src/main.rs?ds=inline diff --git a/src/main.rs b/src/main.rs index d0069e6..c20a47d 100644 --- a/src/main.rs +++ b/src/main.rs @@ -1,11 +1,10 @@ // Welcome to Rust-101 // =================== // -// This is [Rust-101](https://www.ralfj.de/projects/rust-101/), a small *work-in-progress* -// tutorial for the [Rust language](http://www.rust-lang.org/). -// It is intended to be an interactive, hands-on course: I believe the only way to -// *really* learn a language is to write code in it, so you should be coding during -// the course. +// This is [Rust-101](https://www.ralfj.de/projects/rust-101/), a small tutorial for +// the [Rust language](http://www.rust-lang.org/). It is intended to be an interactive, +// hands-on course: I believe the only way to *really* learn a language is to write code +// in it, so you should be coding during the course. // // If you have any questions that are not answered here, check out the "Additional Resources" // below. In particular, the IRC channel is filled with awesome people willing to help you! I spent @@ -18,48 +17,42 @@ // --------- // // When you got here, I am kind of assuming that you already decided to give Rust at -// least a look, so that I don't have to do much convincing here ;-) . But just in +// least a look, so that I don't have to do much convincing here. But just in // case, here's why I think Rust is worth learning:
// At this time, Rust is a language with a pretty unique set of goals. Rust aims to // achieve C++-style control over memory and execution behavior (like, static vs. dynamic // dispatch), which makes it possible to construct abstractions that carry no run-time // cost. This is combined with the comfort of high-level functional languages and guaranteed -// safety (as in, the program will not crash). The vast majority of existing -// languages sacrifices one of these goals for the other. In particular, the -// first requirement rules out a garbage collector: Rust can run "bare metal". -// In fact, Rust rules out more classes of bugs than languages that achieve safety -// with a GC: Besides dangling pointers and double-free, Rust also prevents issues -// such as iterator invalidation and data races. +// safety (as in, the program will not crash in uncontrolled ways). The vast majority of existing +// languages sacrifices control for safety (for example, by enforcing the usage of +// a garbage collector) or vice versa. Rust can run without dynamic allocation (i.e., without +// a heap), and even without an operating system. In fact, Rust rules out more classes of bugs +// than languages that achieve safety with a garbage collector: Besides dangling pointers and +// double-free, Rust also prevents issues such as iterator invalidation and data races. // // // Getting started // --------------- // // You will need to have Rust installed, of course. It is available for download on -// [the Rust website](http://www.rust-lang.org/). Make sure you get at least version 1.2 -// (at the time of writing, that's the current beta release). More detailed installation -// instructions are provided in [the second chapter of The Book](https://doc.rust-lang.org/stable/book/installing-rust.html). +// [the Rust website](http://www.rust-lang.org/). Make sure you get at least version 1.2. +// More detailed installation instructions are provided in +// [the second chapter of The Book](https://doc.rust-lang.org/stable/book/installing-rust.html). // This will also install `cargo`, the tool responsible for building rust projects (or *crates*). - +// // Next, fetch the Rust-101 source code from the [git repository](http://www.ralfj.de/git/rust-101.git) // (also available [on GitHub](https://github.com/RalfJung/rust-101), and as a // [zip archive](https://github.com/RalfJung/rust-101/archive/master.zip) in case you don't have git installed). // // There is a workspace prepared for you in the `workspace` folder. I suggest you copy this -// folder somewhere else - that will make it much easier to later update the course without -// overwriting your changes. Try `cargo build` in that new folder to check that compiling your workspace succeeds. +// folder somewhere else. Try `cargo build` in that new folder to check that compiling your workspace succeeds. // (You can also execute it with `cargo run`, but you'll need to do some work before this will succeed.) -// -// If you later want to update the course, do `git pull` (or re-download the zip archive). -// Then copy the files from `workspace/src/` to your workspace that you did not yet work on. Definitely -// copy `main.rs` to make sure all the new files are actually compiled. (Of course you can also -// copy the rest, but that would replace all your hard work by the original files with all the holes!) // Course Content // -------------- // // Open `your-workspace/src/part00.rs` in your favorite editor, and follow the link below for -// the explanations and exercises. Have fun! +// the explanations and exercises. You are ready to start. Have fun! // // ### Introduction // @@ -120,6 +113,8 @@ fn main() { // of the most interesting places here: // // * [The Rust Book](https://doc.rust-lang.org/stable/book/) +// * [The Rustonomicon](https://doc.rust-lang.org/nightly/nomicon/) // * [Rust by Example](http://rustbyexample.com/) // * The [Rust Subreddit](https://www.reddit.com/r/rust/) +// * A [collection of links](https://github.com/ctjhoa/rust-learning) to blog posts, articles, videos, etc. for learning Rust. // * For the IRC channel and other forums, see the "Community" section of the [Rust Documentation index](http://doc.rust-lang.org/index.html)