bjoernager/rust
bjoernager/rust
1
Fork 0
Code Activity

Rollup merge of #32316 - tclfs:patch-3, r=steveklabnik

Browse source 
docs: `let` introduces a statement

I changes *expression* to *statement* to make more accurate, because in Rust, `let` introduces a declaration statement.
This commit is contained in:
Eduard-Mihai Burtescu 2016-03-19 12:30:01 +02:00
commit cb9b1b26c0
1 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

4
src/doc/book/variable-bindings.md
View file

@ -18,14 +18,14 @@ function, rather than leaving it off. Otherwise, you’ll get an error.
In many languages, a variable binding would be called a *variable*, but Rust’s In many languages, a variable binding would be called a *variable*, but Rust’s
variable bindings have a few tricks up their sleeves. For example the variable bindings have a few tricks up their sleeves. For example the
left-hand side of a `let` expression is a ‘[pattern][pattern]’, not a left-hand side of a `let` statement is a ‘[pattern][pattern]’, not a
variable name. This means we can do things like: variable name. This means we can do things like:
```rust ```rust
let (x, y) = (1, 2); let (x, y) = (1, 2);
``` ```
After this expression is evaluated, `x` will be one, and `y` will be two. After this statement is evaluated, `x` will be one, and `y` will be two.
Patterns are really powerful, and have [their own section][pattern] in the Patterns are really powerful, and have [their own section][pattern] in the
book. We don’t need those features for now, so we’ll keep this in the back book. We don’t need those features for now, so we’ll keep this in the back
of our minds as we go forward. of our minds as we go forward.