A half-hour to learn Rust
👋 This page was last updated ~5 years ago. Just so you know.
In order to increase fluency in a programming language, one has to read a lot of it.
But how can you read a lot of it if you don’t know what it means?
In this article, instead of focusing on one or two concepts, I’ll try to go through as many Rust snippets as I can, and explain what the keywords and symbols they contain mean.
Ready? Go!
[
Variable bindings
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#variable-bindings)[
The let keyword
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#the-let-keyword)
let introduces a variable binding:
_let_ x_;_ _// declare "x"_ x = _42__;_ _// assign 42 to "x"_
This can also be written as a single line:
_let_ x = _42__;_
[
Type annotation
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#type-annotation)
You can specify the variable’s type explicitly with :, that’s a type annotation:
_let_ x_:_ _i32__;_ _// `i32` is a signed 32-bit integer_ x = _42__;_ _// there's i8, i16, i32, i64, i128_ _// also u8, u16, u32, u64, u128 for unsigned_
This can also be written as a single line:
_let_ x_:_ _i32_ = _42__;_
[
Uninitialized variables
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#uninitialized-variables)
If you declare a name and initialize it later, the compiler will prevent you from using it before it’s initialized.
_let_ x_;_ _foobar__(_x_)__;_ _// error: borrow of possibly-uninitialized variable: `x`_ x = _42__;_
However, doing this is completely fine:
_let_ x_;_ x = _42__;_ _foobar__(_x_)__;_ _// the type of `x` will be inferred from here_
[
Throwing values away
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#throwing-values-away)
The underscore _ is a special name - or rather, a “lack of name”. It basically means to throw away something:
_// this does *nothing* because 42 is a constant_ _let_ _ = _42__;_ _// this calls `get_thing` but throws away its result_ _let_ _ = _get_thing__(__)__;_
Names that start with an underscore are regular names, it’s just that the compiler won’t warn about them being unused:
_// we may use `_x` eventually, but our code is a work-in-progress_ _// and we just wanted to get rid of a compiler warning for now._ _let_ _x = _42__;_
[
Shadowing bindings
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#shadowing-bindings)
Separate bindings with the same name can be introduced - you can shadow a variable binding:
_let_ x = _13__;_ _let_ x = x + _3__;_ _// using `x` after that line only refers to the second `x`,_ _//_ _// although the first `x` still exists (it'll be dropped_ _// when going out of scope), you can no longer refer to it._
[
Tuples
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#tuples)
Rust has tuples, which you can think of as “fixed-length collections of values of different types”.
_let_ pair = _(__'a'__,_ _17__)__;_ pair_.__0__;_ _// this is 'a'_ pair_.__1__;_ _// this is 17_
If we really wanted to annotate the type of pair, we would write:
_let_ pair_:_ _(__char__,_ _i32__)_ = _(__'a'__,_ _17__)__;_
[
Destructuring tuples
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#destructuring-tuples)
Tuples can be destructured when doing an assignment, which means they’re broken down into their individual fields:
_let_ _(_some_char_,_ some_int_)_ = _(__'a'__,_ _17__)__;_ _// now, `some_char` is 'a', and `some_int` is 17_
This is especially useful when a function returns a tuple:
_let_ _(_left_,_ right_)_ = slice_.__split_at__(_middle_)__;_
Of course, when destructuring a tuple, _ can be used to throw away part of it:
_let_ _(___,_ right_)_ = slice_.__split_at__(_middle_)__;_
[
Statements
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#statements)
The semi-colon marks the end of a statement:
_let_ x = _3__;_ _let_ y = _5__;_ _let_ z = y + x_;_
Which means statements can span multiple lines:
_let_ x = _vec__!__[__1__,_ _2__,_ _3__,_ _4__,_ _5__,_ _6__,_ _7__,_ _8__]_ _.__iter__(__)_ _.__map__(_|x| x + _3__)_ _.__fold__(__0__,_ |x_,_ y| x + y_)__;_
(We’ll go over what those actually mean later).
[
Functions
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#functions)
fn declares a function.
Here’s a void function:
_fn_ _greet__(__)_ _{_ _println__!__(__"Hi there!"__)__;_ _}_
And here’s a function that returns a 32-bit signed integer. The arrow indicates its return type:
_fn_ _fair_dice_roll__(__)_ -> _i32_ _{_ _4_ _}_
[
Blocks
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#blocks)
A pair of brackets declares a block, which has its own scope:
_// This prints "in", then "out"_ _fn_ _main__(__)_ _{_ _let_ x = _"out"__;_ _{_ _// this is a different `x`_ _let_ x = _"in"__;_ _println__!__(__"{}"__,_ x_)__;_ _}_ _println__!__(__"{}"__,_ x_)__;_ _}_
[
Blocks are expressions
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#blocks-are-expressions)
Blocks are also expressions, which mean they evaluate to a value.
_// this:_ _let_ x = _42__;_ _// is equivalent to this:_ _let_ x = _{_ _42_ _}__;_
Inside a block, there can be multiple statements:
_let_ x = _{_ _let_ y = _1__;_ _// first statement_ _let_ z = _2__;_ _// second statement_ y + z _// this is the *tail* - what the whole block will evaluate to_ _}__;_
[
Implicit return
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#implicit-return)
And that’s why “omitting the semicolon at the end of a function” is the same as returning, ie. these are equivalent:
_fn_ _fair_dice_roll__(__)_ -> _i32_ _{_ _return_ _4__;_ _}_ _fn_ _fair_dice_roll__(__)_ -> _i32_ _{_ _4_ _}_
[
Everything is an expression
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#everything-is-an-expression)
if conditionals are also expressions:
_fn_ _fair_dice_roll__(__)_ -> _i32_ _{_ _if_ feeling_lucky _{_ _6_ _}_ _else_ _{_ _4_ _}_ _}_
A match is also an expression:
_fn_ _fair_dice_roll__(__)_ -> _i32_ _{_ _match_ feeling_lucky _{_ _true_ => _6__,_ _false_ => _4__,_ _}_ _}_
[
Field access and method calling
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#field-access-and-method-calling)
Dots are typically used to access fields of a value:
_let_ a = _(__10__,_ _20__)__;_ a_.__0__;_ _// this is 10_ _let_ amos = _get_some_struct__(__)__;_ amos_.__nickname__;_ _// this is "fasterthanlime"_
Or call a method on a value:
_let_ nick = _"fasterthanlime"__;_ nick_.__len__(__)__;_ _// this is 14_
[
Modules, use syntax
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#modules-use-syntax)
The double-colon, ::, is similar but it operates on namespaces.
In this example, std is a crate (~ a library), cmp is a module (~ a source file), and min is a function:
_let_ least = std_::_cmp_::__min__(__3__,_ _8__)__;_ _// this is 3_
use directives can be used to “bring in scope” names from other namespace:
_use_ std_::_cmp_::_min_;_ _let_ least = _min__(__7__,_ _1__)__;_ _// this is 1_
Within use directives, curly brackets have another meaning: they’re “globs”. If we want to import both min and max, we can do any of these:
_// this works:_ _use_ std_::_cmp_::_min_;_ _use_ std_::_cmp_::_max_;_ _// this also works:_ _use_ std_::_cmp_::__{_min_,_ max_}__;_ _// this also works!_ _use_ std_::__{_cmp_::_min_,_ cmp_::_max_}__;_
A wildcard (*) lets you import every symbol from a namespace:
_// this brings `min` and `max` in scope, and many other things_ _use_ std_::_cmp_::__*__;_
[
Types are namespaces too
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#types-are-namespaces-too)
Types are namespaces too, and methods can be called as regular functions:
_let_ x = _"amos"__.__len__(__)__;_ _// this is 4_ _let_ x = str_::__len__(__"amos"__)__;_ _// this is also 4_
[
The libstd prelude
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#the-libstd-prelude)
str is a primitive type, but many non-primitive types are also in scope by default.
_// `Vec` is a regular struct, not a primitive type_ _let_ v = _Vec__::__new__(__)__;_ _// this is exactly the same code, but with the *full* path to `Vec`_ _let_ v = std_::_vec_::__Vec__::__new__(__)__;_
This works because Rust inserts this at the beginning of every module:
_use_ std_::_prelude_::_v1_::__*__;_
(Which in turns re-exports a lot of symbols, like Vec, String, Option and Result).
[
Structs
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#structs)
Structs are declared with the struct keyword:
_struct_ _Vec2_ _{_ _x__:_ _f64__,_ _// 64-bit floating point, aka "double precision"_ _y__:_ _f64__,_ _}_
They can be initialized using struct literals:
_let_ v1 = _Vec2_ _{_ _x__:_ _1.0__,_ _y__:_ _3.0_ _}__;_ _let_ v2 = _Vec2_ _{_ _y__:_ _2.0__,_ _x__:_ _4.0_ _}__;_ _// the order does not matter, only the names do_
[
Struct update syntax
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#struct-update-syntax)
There is a shortcut for initializing the rest of the fields from another struct:
_let_ v3 = _Vec2_ _{_ _x__:_ _14.0__,_ ..v2 _}__;_
This is called “struct update syntax”, can only happen in last position, and cannot be followed by a comma.
Note that the rest of the fields can mean all the fields:
_let_ v4 = _Vec2_ _{_ ..v3 _}__;_
[
Destructuring structs
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#destructuring-structs)
Structs, like tuples, can be destructured.
Just like this is a valid let pattern:
_let_ _(_left_,_ right_)_ = slice_.__split_at__(_middle_)__;_
So is this:
_let_ v = _Vec2_ _{_ _x__:_ _3.0__,_ _y__:_ _6.0_ _}__;_ _let_ _Vec2_ _{_ x_,_ y _}_ = v_;_ _// `x` is now 3.0, `y` is now `6.0`_
And this:
_let_ _Vec2_ _{_ x_,_ .. _}_ = v_;_ _// this throws away `v.y`_
[
Patterns and destructuring
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#patterns-and-destructuring)[
Destructuring with if let
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#destructuring-with-if-let)
let patterns can be used as conditions in if:
_struct_ _Number_ _{_ _odd__:_ _bool__,_ _value__:_ _i32__,_ _}_ _fn_ _main__(__)_ _{_ _let_ one = _Number_ _{_ _odd__:_ _true__,_ _value__:_ _1_ _}__;_ _let_ two = _Number_ _{_ _odd__:_ _false__,_ _value__:_ _2_ _}__;_ _print_number__(_one_)__;_ _print_number__(_two_)__;_ _}_ _fn_ _print_number__(__n__:_ _Number__)_ _{_ _if_ _let_ _Number_ _{_ _odd__:_ _true__,_ value _}_ = n _{_ _println__!__(__"Odd number: {}"__,_ value_)__;_ _}_ _else_ _if_ _let_ _Number_ _{_ _odd__:_ _false__,_ value _}_ = n _{_ _println__!__(__"Even number: {}"__,_ value_)__;_ _}_ _}_ _// this prints:_ _// Odd number: 1_ _// Even number: 2_
[
Match arms are patterns
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#match-arms-are-patterns)
match arms are also patterns, just like if let:
_fn_ _print_number__(__n__:_ _Number__)_ _{_ _match_ n _{_ _Number_ _{_ _odd__:_ _true__,_ value _}_ => _println__!__(__"Odd number: {}"__,_ value_)__,_ _Number_ _{_ _odd__:_ _false__,_ value _}_ => _println__!__(__"Even number: {}"__,_ value_)__,_ _}_ _}_ _// this prints the same as before_
[
Exhaustive matches
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#exhaustive-matches)
A match has to be exhaustive: at least one arm needs to match.
_fn_ _print_number__(__n__:_ _Number__)_ _{_ _match_ n _{_ _Number_ _{_ _value__:_ _1__,_ .. _}_ => _println__!__(__"One"__)__,_ _Number_ _{_ _value__:_ _2__,_ .. _}_ => _println__!__(__"Two"__)__,_ _Number_ _{_ value_,_ .. _}_ => _println__!__(__"{}"__,_ value_)__,_ _// if that last arm didn't exist, we would get a compile-time error_ _}_ _}_
If that’s hard, _ can be used as a “catch-all” pattern:
_fn_ _print_number__(__n__:_ _Number__)_ _{_ _match_ n_.__value_ _{_ _1_ => _println__!__(__"One"__)__,_ _2_ => _println__!__(__"Two"__)__,_ _ => _println__!__(__"{}"__,_ n_._value_)__,_ _}_ _}_
[
Methods
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#methods)
You can declare methods on your own types:
_struct_ _Number_ _{_ _odd__:_ _bool__,_ _value__:_ _i32__,_ _}_ _impl_ _Number_ _{_ _fn_ _is_strictly_positive__(__self__)_ -> _bool_ _{_ _self__.__value_ > _0_ _}_ _}_
And use them like usual:
_fn_ _main__(__)_ _{_ _let_ minus_two = _Number_ _{_ _odd__:_ _false__,_ _value__:_ -_2__,_ _}__;_ _println__!__(__"positive? {}"__,_ minus_two_._is_strictly_positive_(__)__)__;_ _// this prints "positive? false"_ _}_
[
Immutability
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#immutability)
Variable bindings are immutable by default, which means their interior can’t be mutated:
_fn_ _main__(__)_ _{_ _let_ n = _Number_ _{_ _odd__:_ _true__,_ _value__:_ _17__,_ _}__;_ n_.__odd_ = _false__;_ _// error: cannot assign to `n.odd`,_ _// as `n` is not declared to be mutable_ _}_
And also that they cannot be assigned to:
_fn_ _main__(__)_ _{_ _let_ n = _Number_ _{_ _odd__:_ _true__,_ _value__:_ _17__,_ _}__;_ n = _Number_ _{_ _odd__:_ _false__,_ _value__:_ _22__,_ _}__;_ _// error: cannot assign twice to immutable variable `n`_ _}_
mut makes a variable binding mutable:
_fn_ _main__(__)_ _{_ _let_ _mut_ n = _Number_ _{_ _odd__:_ _true__,_ _value__:_ _17__,_ _}_ n_.__value_ = _19__;_ _// all good_ _}_
[
Traits
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#traits)
Traits are something multiple types can have in common:
_trait_ _Signed_ _{_ _fn_ _is_strictly_negative__(__self__)_ -> _bool__;_ _}_
[
Orphan rules
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#orphan-rules)
You can implement:
- one of your traits on anyone’s type
- anyone’s trait on one of your types
- but not a foreign trait on a foreign type
These are called the “orphan rules”.
Here’s an implementation of our trait on our type:
_impl_ _Signed_ _for_ _Number_ _{_ _fn_ _is_strictly_negative__(__self__)_ -> _bool_ _{_ _self__.__value_ < _0_ _}_ _}_ _fn_ _main__(__)_ _{_ _let_ n = _Number_ _{_ _odd__:_ _false__,_ _value__:_ -_44_ _}__;_ _println__!__(__"{}"__,_ n_._is_strictly_negative_(__)__)__;_ _// prints "true"_ _}_
Our trait on a foreign type (a primitive type, even):
_impl_ _Signed_ _for_ _i32_ _{_ _fn_ _is_strictly_negative__(__self__)_ -> _bool_ _{_ _self_ < _0_ _}_ _}_ _fn_ _main__(__)_ _{_ _let_ n_:_ _i32_ = -_44__;_ _println__!__(__"{}"__,_ n_._is_strictly_negative_(__)__)__;_ _// prints "true"_ _}_
A foreign trait on our type:
_// the `Neg` trait is used to overload `-`, the_ _// unary minus operator._ _impl_ std_::_ops_::__Neg_ _for_ _Number_ _{_ _type_ _Output_ = _Number__;_ _fn_ _neg__(__self__)_ -> _Number_ _{_ _Number_ _{_ _value__:_ -_self__.__value__,_ _odd__:_ _self__.__odd__,_ _}_ _}_ _}_ _fn_ _main__(__)_ _{_ _let_ n = _Number_ _{_ _odd__:_ _true__,_ _value__:_ _987_ _}__;_ _let_ m = -n_;_ _// this is only possible because we implemented `Neg`_ _println__!__(__"{}"__,_ m_._value_)__;_ _// prints "-987"_ _}_
[
The Self type
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#the-self-type)
An impl block is always for a type, so, inside that block, Self means that type:
_impl_ std_::_ops_::__Neg_ _for_ _Number_ _{_ _type_ _Output_ = _Self__;_ _fn_ _neg__(__self__)_ -> _Self_ _{_ _Self_ _{_ _value__:_ -_self__.__value__,_ _odd__:_ _self__.__odd__,_ _}_ _}_ _}_
[
Marker traits
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#marker-traits)
Some traits are markers - they don’t say that a type implements some methods, they say that certain things can be done with a type.
For example, i32 implements trait Copy (in short, i32 is Copy), so this works:
_fn_ _main__(__)_ _{_ _let_ a_:_ _i32_ = _15__;_ _let_ b = a_;_ _// `a` is copied_ _let_ c = a_;_ _// `a` is copied again_ _}_
And this also works:
_fn_ _print_i32__(__x__:_ _i32__)_ _{_ _println__!__(__"x = {}"__,_ x_)__;_ _}_ _fn_ _main__(__)_ _{_ _let_ a_:_ _i32_ = _15__;_ _print_i32__(_a_)__;_ _// `a` is copied_ _print_i32__(_a_)__;_ _// `a` is copied again_ _}_
But the Number struct is not Copy, so this doesn’t work:
_fn_ _main__(__)_ _{_ _let_ n = _Number_ _{_ _odd__:_ _true__,_ _value__:_ _51_ _}__;_ _let_ m = n_;_ _// `n` is moved into `m`_ _let_ o = n_;_ _// error: use of moved value: `n`_ _}_
And neither does this:
_fn_ _print_number__(__n__:_ _Number__)_ _{_ _println__!__(__"{} number {}"__,_ _if_ n_._odd _{_ _"odd"_ _}_ else _{_ _"even"_ _}__,_ n_._value_)__;_ _}_ _fn_ _main__(__)_ _{_ _let_ n = _Number_ _{_ _odd__:_ _true__,_ _value__:_ _51_ _}__;_ _print_number__(_n_)__;_ _// `n` is moved_ _print_number__(_n_)__;_ _// error: use of moved value: `n`_ _}_
But it works if print_number takes an immutable reference instead:
_fn_ _print_number__(__n__:_ _&__Number__)_ _{_ _println__!__(__"{} number {}"__,_ _if_ n_._odd _{_ _"odd"_ _}_ else _{_ _"even"_ _}__,_ n_._value_)__;_ _}_ _fn_ _main__(__)_ _{_ _let_ n = _Number_ _{_ _odd__:_ _true__,_ _value__:_ _51_ _}__;_ _print_number__(__&_n_)__;_ _// `n` is borrowed for the time of the call_ _print_number__(__&_n_)__;_ _// `n` is borrowed again_ _}_
It also works if a function takes a mutable reference - but only if our variable binding is also mut.
_fn_ _invert__(__n__:_ _&__mut_ _Number__)_ _{_ n_.__value_ = -n_.__value__;_ _}_ _fn_ _print_number__(__n__:_ _&__Number__)_ _{_ _println__!__(__"{} number {}"__,_ _if_ n_._odd _{_ _"odd"_ _}_ else _{_ _"even"_ _}__,_ n_._value_)__;_ _}_ _fn_ _main__(__)_ _{_ _// this time, `n` is mutable_ _let_ _mut_ n = _Number_ _{_ _odd__:_ _true__,_ _value__:_ _51_ _}__;_ _print_number__(__&_n_)__;_ _invert__(__&__mut_ n_)__;_ _// `n is borrowed mutably - everything is explicit_ _print_number__(__&_n_)__;_ _}_
[
Trait method receivers
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#trait-method-receivers)
Trait methods can also take self by reference or mutable reference:
_impl_ std_::_clone_::__Clone_ _for_ _Number_ _{_ _fn_ _clone__(__&__self__)_ -> _Self_ _{_ _Self_ _{_ .._*__self_ _}_ _}_ _}_
When invoking trait methods, the receiver is borrowed implicitly:
_fn_ _main__(__)_ _{_ _let_ n = _Number_ _{_ _odd__:_ _true__,_ _value__:_ _51_ _}__;_ _let_ _mut_ m = n_.__clone__(__)__;_ m_.__value_ += _100__;_ _print_number__(__&_n_)__;_ _print_number__(__&_m_)__;_ _}_
To highlight this: these are equivalent:
_let_ m = n_.__clone__(__)__;_ _let_ m = std_::_clone_::__Clone__::__clone__(__&_n_)__;_
Marker traits like Copy have no methods:
_// note: `Copy` requires that `Clone` is implemented too_ _impl_ std_::_clone_::__Clone_ _for_ _Number_ _{_ _fn_ _clone__(__&__self__)_ -> _Self_ _{_ _Self_ _{_ .._*__self_ _}_ _}_ _}_ _impl_ std_::_marker_::__Copy_ _for_ _Number_ _{__}_
Now, Clone can still be used:
_fn_ _main__(__)_ _{_ _let_ n = _Number_ _{_ _odd__:_ _true__,_ _value__:_ _51_ _}__;_ _let_ m = n_.__clone__(__)__;_ _let_ o = n_.__clone__(__)__;_ _}_
But Number values will no longer be moved:
_fn_ _main__(__)_ _{_ _let_ n = _Number_ _{_ _odd__:_ _true__,_ _value__:_ _51_ _}__;_ _let_ m = n_;_ _// `m` is a copy of `n`_ _let_ o = n_;_ _// same. `n` is neither moved nor borrowed._ _}_
[
Deriving traits
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#deriving-traits)
Some traits are so common, they can be implemented automatically by using the derive attribute:
_#_[_derive_(_Clone_,_ Copy_)__]__ _struct_ _Number_ _{_ _odd__:_ _bool__,_ _value__:_ _i32__,_ _}_ _// this expands to `impl Clone for Number` and `impl Copy for Number` blocks._
[
Generics
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#generics)[
Generic functions
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#generic-functions)
Functions can be generic:
_fn_ _foobar__<__T__>__(__arg__:_ _T__)_ _{_ _// do something with `arg`_ _}_
They can have multiple type parameters, which can then be used in the function’s declaration and its body, instead of concrete types:
_fn_ _foobar__<__L__,_ _R__>__(__left__:_ _L__,_ _right__:_ _R__)_ _{_ _// do something with `left` and `right`_ _}_
[
Type parameter constraints (trait bounds)
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#type-parameter-constraints-trait-bounds)
Type parameters usually have constraints, so you can actually do something with them.
The simplest constraints are just trait names:
_fn_ _print__<__T__:_ _Display__>__(__value__:_ _T__)_ _{_ _println__!__(__"value = {}"__,_ value_)__;_ _}_ _fn_ _print__<__T__:_ _Debug__>__(__value__:_ _T__)_ _{_ _println__!__(__"value = {:?}"__,_ value_)__;_ _}_
There’s a longer syntax for type parameter constraints:
_fn_ _print__<__T__>__(__value__:_ _T__)_ _where_ _T__:_ _Display__,_ _{_ _println__!__(__"value = {}"__,_ value_)__;_ _}_
Constraints can be more complicated: they can require a type parameter to implement multiple traits:
_use_ std_::_fmt_::_Debug_;_ _fn_ _compare__<__T__>__(__left__:_ _T__,_ _right__:_ _T__)_ _where_ _T__:_ _Debug_ + _PartialEq__,_ _{_ _println__!__(__"{:?} {} {:?}"__,_ left_,_ _if_ left == right _{_ _"=="_ _}_ else _{_ _"!="_ _}__,_ right_)__;_ _}_ _fn_ _main__(__)_ _{_ _compare__(__"tea"__,_ _"coffee"__)__;_ _// prints: "tea" != "coffee"_ _}_
[
Monomorphization
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#monomorphization)
Generic functions can be thought of as namespaces, containing an infinity of functions with different concrete types.
Same as with crates, and modules, and types, generic functions can be “explored” (navigated?) using ::
_fn_ _main__(__)_ _{_ _use_ std_::_any_::_type_name_;_ _println__!__(__"{}"__,_ type_name_::_<_i32_>_(__)__)__;_ _// prints "i32"_ _println__!__(__"{}"__,_ type_name_::_<_(__f64__,_ _char__)_>_(__)__)__;_ _// prints "(f64, char)"_ _}_
This is lovingly called turbofish syntax, because ::<> looks like a fish.
[
Generic structs
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#generic-structs)
Structs can be generic too:
_struct_ _Pair__<__T__>_ _{_ _a__:_ _T__,_ _b__:_ _T__,_ _}_ _fn_ _print_type_name__<__T__>__(___val__:_ _&__T__)_ _{_ _println__!__(__"{}"__,_ std_::_any_::_type_name_::_<T>_(__)__)__;_ _}_ _fn_ _main__(__)_ _{_ _let_ p1 = _Pair_ _{_ _a__:_ _3__,_ _b__:_ _9_ _}__;_ _let_ p2 = _Pair_ _{_ _a__:_ _true__,_ _b__:_ _false_ _}__;_ _print_type_name__(__&_p1_)__;_ _// prints "Pair<i32>"_ _print_type_name__(__&_p2_)__;_ _// prints "Pair<bool>"_ _}_
[
Example: Vec<T>
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#example-vec-t)
The standard library type Vec (~ a heap-allocated array), is generic:
_fn_ _main__(__)_ _{_ _let_ _mut_ v1 = _Vec__::__new__(__)__;_ v1_.__push__(__1__)__;_ _let_ _mut_ v2 = _Vec__::__new__(__)__;_ v2_.__push__(__false__)__;_ _print_type_name__(__&_v1_)__;_ _// prints "Vec<i32>"_ _print_type_name__(__&_v2_)__;_ _// prints "Vec<bool>"_ _}_
Speaking of Vec, it comes with a macro that gives more or less “vec literals”:
_fn_ _main__(__)_ _{_ _let_ v1 = _vec__!__[__1__,_ _2__,_ _3__]__;_ _let_ v2 = _vec__!__[__true__,_ _false__,_ _true__]__;_ _print_type_name__(__&_v1_)__;_ _// prints "Vec<i32>"_ _print_type_name__(__&_v2_)__;_ _// prints "Vec<bool>"_ _}_
[
Macros
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#macros)
All of name!(), name![] or name!{} invoke a macro. Macros just expand to regular code.
In fact, println is a macro:
_fn_ _main__(__)_ _{_ _println__!__(__"{}"__,_ _"Hello there!"__)__;_ _}_
This expands to something that has the same effect as:
_fn_ _main__(__)_ _{_ _use_ std_::_io_::__{__self__,_ Write_}__;_ io_::__stdout__(__)__.__lock__(__)__.__write_all__(__b"Hello there!\n"__)__.__unwrap__(__)__;_ _}_
[
The panic! macro
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#the-panic-macro)
panic is also a macro. It violently stops execution with an error message, and the file name / line number of the error, if enabled:
_fn_ _main__(__)_ _{_ _panic__!__(__"This panics"__)__;_ _}_ _// output: thread 'main' panicked at 'This panics', src/main.rs:3:5_
[
Functions that panic
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#functions-that-panic)
Some methods also panic. For example, the Option type can contain something, or it can contain nothing. If .unwrap() is called on it, and it contains nothing, it panics:
_fn_ _main__(__)_ _{_ _let_ o1_:_ _Option__<__i32__>_ = _Some__(__128__)__;_ o1_.__unwrap__(__)__;_ _// this is fine_ _let_ o2_:_ _Option__<__i32__>_ = None_;_ o2_.__unwrap__(__)__;_ _// this panics!_ _}_ _// output: thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', src/libcore/option.rs:378:21_
[
Enums (sum types)
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#enums-sum-types)
Option is not a struct - it’s an enum, with two variants.
_enum_ _Option__<__T__>_ _{_ None_,_ Some_(__T__)__,_ _}_ _impl__<__T__>_ _Option__<__T__>_ _{_ _fn_ _unwrap__(__self__)_ -> _T_ _{_ _// enums variants can be used in patterns:_ _match_ _self_ _{_ _Self__::_Some_(_t_)_ => t_,_ _Self__::_None => _panic__!__(__".unwrap() called on a None option"__)__,_ _}_ _}_ _}_ _use_ _self__::_Option_::__{_None_,_ Some_}__;_ _fn_ _main__(__)_ _{_ _let_ o1_:_ _Option__<__i32__>_ = _Some__(__128__)__;_ o1_.__unwrap__(__)__;_ _// this is fine_ _let_ o2_:_ _Option__<__i32__>_ = None_;_ o2_.__unwrap__(__)__;_ _// this panics!_ _}_ _// output: thread 'main' panicked at '.unwrap() called on a None option', src/main.rs:11:27_
Result is also an enum, it can either contain something, or an error:
_enum_ _Result__<__T__,_ _E__>_ _{_ Ok_(__T__)__,_ Err_(__E__)__,_ _}_
It also panics when unwrapped and containing an error.
[
Lifetimes
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#lifetimes)
Variables bindings have a “lifetime”:
_fn_ _main__(__)_ _{_ _// `x` doesn't exist yet_ _{_ _let_ x = _42__;_ _// `x` starts existing_ _println__!__(__"x = {}"__,_ x_)__;_ _// `x` stops existing_ _}_ _// `x` no longer exists_ _}_
Similarly, references have a lifetime:
_fn_ _main__(__)_ _{_ _// `x` doesn't exist yet_ _{_ _let_ x = _42__;_ _// `x` starts existing_ _let_ x_ref = _&_x_;_ _// `x_ref` starts existing - it borrows `x`_ _println__!__(__"x_ref = {}"__,_ x_ref_)__;_ _// `x_ref` stops existing_ _// `x` stops existing_ _}_ _// `x` no longer exists_ _}_
The lifetime of a reference cannot exceed the lifetime of the variable binding it borrows:
_fn_ _main__(__)_ _{_ _let_ x_ref = _{_ _let_ x = _42__;_ _&_x _}__;_ _println__!__(__"x_ref = {}"__,_ x_ref_)__;_ _// error: `x` does not live long enough_ _}_
[
Borrowing rules (one or more immutable borrows XOR one mutable borrow)
A variable binding can be immutably borrowed multiple times:
_fn_ _main__(__)_ _{_ _let_ x = _42__;_ _let_ x_ref1 = _&_x_;_ _let_ x_ref2 = _&_x_;_ _let_ x_ref3 = _&_x_;_ _println__!__(__"{} {} {}"__,_ x_ref1_,_ x_ref2_,_ x_ref3_)__;_ _}_
While borrowed, a variable binding cannot be mutated:
_fn_ _main__(__)_ _{_ _let_ _mut_ x = _42__;_ _let_ x_ref = _&_x_;_ x = _13__;_ _println__!__(__"x_ref = {}"__,_ x_ref_)__;_ _// error: cannot assign to `x` because it is borrowed_ _}_
While immutably borrowed, a variable cannot be mutably borrowed:
_fn_ _main__(__)_ _{_ _let_ _mut_ x = _42__;_ _let_ x_ref1 = _&_x_;_ _let_ x_ref2 = _&__mut_ x_;_ _// error: cannot borrow `x` as mutable because it is also borrowed as immutable_ _println__!__(__"x_ref1 = {}"__,_ x_ref1_)__;_ _}_
[
Functions generic over lifetimes
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#functions-generic-over-lifetimes)
References in function arguments also have lifetimes:
_fn_ _print__(__x__:_ _&__i32__)_ _{_ _// `x` is borrowed (from the outside) for the_ _// entire time this function is called._ _}_
Functions with reference arguments can be called with borrows that have different lifetimes, so:
- All functions that take references are generic
- Lifetimes are generic parameters
Lifetimes’ names start with a single quote, ':
_// elided (non-named) lifetimes:_ _fn_ _print__(__x__:_ _&__i32__)_ _{__}_ _// named lifetimes:_ _fn_ _print__<__'__a__>__(__x__:_ _&__'__a_ _i32__)_ _{__}_
This allows returning references whose lifetime depend on the lifetime of the arguments:
_struct_ _Number_ _{_ _value__:_ _i32__,_ _}_ _fn_ _number_value__<__'__a__>__(__num__:_ _&__'__a_ _Number__)_ -> _&__'__a_ _i32_ _{_ _&_num_.__value_ _}_ _fn_ _main__(__)_ _{_ _let_ n = _Number_ _{_ _value__:_ _47_ _}__;_ _let_ v = _number_value__(__&_n_)__;_ _// `v` borrows `n` (immutably), thus: `v` cannot outlive `n`._ _// While `v` exists, `n` cannot be mutably borrowed, mutated, moved, etc._ _}_
[
Lifetime elision
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#lifetime-elision)
When there is a single input lifetime, it doesn’t need to be named, and everything has the same lifetime, so the two functions below are equivalent:
_fn_ _number_value__<__'__a__>__(__num__:_ _&__'__a_ _Number__)_ -> _&__'__a_ _i32_ _{_ _&_num_.__value_ _}_ _fn_ _number_value__(__num__:_ _&__Number__)_ -> _&__i32_ _{_ _&_num_.__value_ _}_
[
Structs generic over lifetimes
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#structs-generic-over-lifetimes)
Structs can also be generic over lifetimes, which allows them to hold references:
_struct_ _NumRef__<__'__a__>_ _{_ _x__:_ _&__'__a_ _i32__,_ _}_ _fn_ _main__(__)_ _{_ _let_ x_:_ _i32_ = _99__;_ _let_ x_ref = _NumRef_ _{_ _x__:_ _&_x _}__;_ _// `x_ref` cannot outlive `x`, etc._ _}_
The same code, but with an additional function:
_struct_ _NumRef__<__'__a__>_ _{_ _x__:_ _&__'__a_ _i32__,_ _}_ _fn_ _as_num_ref__<__'__a__>__(__x__:_ _&__'__a_ _i32__)_ -> _NumRef__<__'__a__>_ _{_ _NumRef_ _{_ _x__:_ _&_x _}_ _}_ _fn_ _main__(__)_ _{_ _let_ x_:_ _i32_ = _99__;_ _let_ x_ref = _as_num_ref__(__&_x_)__;_ _// `x_ref` cannot outlive `x`, etc._ _}_
The same code, but with “elided” lifetimes:
_struct_ _NumRef__<__'__a__>_ _{_ _x__:_ _&__'__a_ _i32__,_ _}_ _fn_ _as_num_ref__(__x__:_ _&__i32__)_ -> _NumRef__<__'_____>_ _{_ _NumRef_ _{_ _x__:_ _&_x _}_ _}_ _fn_ _main__(__)_ _{_ _let_ x_:_ _i32_ = _99__;_ _let_ x_ref = _as_num_ref__(__&_x_)__;_ _// `x_ref` cannot outlive `x`, etc._ _}_
[
Implementations generic over lifetimes
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#implementations-generic-over-lifetimes)
impl blocks can be generic over lifetimes too:
_impl__<__'__a__>_ _NumRef__<__'__a__>_ _{_ _fn_ _as_i32_ref__(__&__'__a_ _self__)_ -> _&__'__a_ _i32_ _{_ _self__.__x_ _}_ _}_ _fn_ _main__(__)_ _{_ _let_ x_:_ _i32_ = _99__;_ _let_ x_num_ref = _NumRef_ _{_ _x__:_ _&_x _}__;_ _let_ x_i32_ref = x_num_ref_.__as_i32_ref__(__)__;_ _// neither ref can outlive `x`_ _}_
But you can do elision (“to elide”) there too:
_impl__<__'__a__>_ _NumRef__<__'__a__>_ _{_ _fn_ _as_i32_ref__(__&__self__)_ -> _&__i32_ _{_ _self__.__x_ _}_ _}_
You can elide even harder, if you never need the name:
_impl_ _NumRef__<__'_____>_ _{_ _fn_ _as_i32_ref__(__&__self__)_ -> _&__i32_ _{_ _self__.__x_ _}_ _}_
[
The 'static lifetime
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#the-static-lifetime)
There is a special lifetime, named 'static, which is valid for the entire program’s lifetime.
String literals are 'static:
_struct_ _Person_ _{_ _name__:_ _&__'__static_ _str__,_ _}_ _fn_ _main__(__)_ _{_ _let_ p = _Person_ _{_ _name__:_ _"fasterthanlime"__,_ _}__;_ _}_
But references to a String are not static:
_struct_ _Person_ _{_ _name__:_ _&__'__static_ _str__,_ _}_ _fn_ _main__(__)_ _{_ _let_ name = _format__!__(__"fasterthan{}"__,_ _"lime"__)__;_ _let_ p = _Person_ _{_ _name__:_ _&_name _}__;_ _// error: `name` does not live long enough_ _}_
In that last example, the local name is not a &'static str, it’s a String. It’s been allocated dynamically, and it will be freed. Its lifetime is less than the whole program (even though it happens to be in main).
To store a non-'static string in Person, it needs to either:
A) Be generic over a lifetime:
_struct_ _Person__<__'__a__>_ _{_ _name__:_ _&__'__a_ _str__,_ _}_ _fn_ _main__(__)_ _{_ _let_ name = _format__!__(__"fasterthan{}"__,_ _"lime"__)__;_ _let_ p = _Person_ _{_ _name__:_ _&_name _}__;_ _// `p` cannot outlive `name`_ _}_
or
B) Take ownership of the string
_struct_ _Person_ _{_ _name__:_ _String__,_ _}_ _fn_ _main__(__)_ _{_ _let_ name = _format__!__(__"fasterthan{}"__,_ _"lime"__)__;_ _let_ p = _Person_ _{_ _name__:_ name _}__;_ _// `name` was moved into `p`, their lifetimes are no longer tied._ _}_
[
Struct literal assignment shorthand
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#struct-literal-assignment-shorthand)
Speaking of: in a struct literal, when a field is set to a variable binding of the same name:
_let_ p = _Person_ _{_ _name__:_ name _}__;_
It can be shortened like this:
_let_ p = _Person_ _{_ name _}__;_
Tools like clippy will suggest making those changes, and even apply the fix programmatically if you let it.
[
Owned types vs reference types
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#owned-types-vs-reference-types)
For many types in Rust, there are owned and non-owned variants:
- Strings:
Stringis owned,&stris a reference. - Paths:
PathBufis owned,&Pathis a reference. - Collections:
Vec<T>is owned,&[T]is a reference.
[
Slices
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#slices)
Rust has slices - they’re a reference to multiple contiguous elements.
You can borrow a slice of a vector, for example:
_fn_ _main__(__)_ _{_ _let_ v = _vec__!__[__1__,_ _2__,_ _3__,_ _4__,_ _5__]__;_ _let_ v2 = _&_v_[__2_.._4__]__;_ _println__!__(__"v2 = {:?}"__,_ v2_)__;_ _}_ _// output:_ _// v2 = [3, 4]_
[
Operator overloading
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#operator-overloading)
The above is not magical. The indexing operator (foo[index]) is overloaded with the Index and IndexMut traits.
The .. syntax is just range literals. Ranges are just a few structs defined in the standard library.
They can be open-ended, and their rightmost bound can be inclusive, if it’s preceded by =.
_fn_ _main__(__)_ _{_ _// 0 or greater_ _println__!__(__"{:?}"__,_ _(__0_.._)__._contains_(__&__100__)__)__;_ _// true_ _// strictly less than 20_ _println__!__(__"{:?}"__,_ _(_.._20__)__._contains_(__&__20__)__)__;_ _// false_ _// 20 or less than 20_ _println__!__(__"{:?}"__,_ _(_..=_20__)__._contains_(__&__20__)__)__;_ _// true_ _// only 3, 4, 5_ _println__!__(__"{:?}"__,_ _(__3_.._6__)__._contains_(__&__4__)__)__;_ _// true_ _}_
[
Borrowing rules and slices
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#borrowing-rules-and-slices)
Borrowing rules apply to slices.
_fn_ _tail__(__s__:_ _&__[__u8__]__)_ -> _&__[__u8__]_ _{_ _&_s_[__1_.._]_ _}_ _fn_ _main__(__)_ _{_ _let_ x = _&__[__1__,_ _2__,_ _3__,_ _4__,_ _5__]__;_ _let_ y = _tail__(_x_)__;_ _println__!__(__"y = {:?}"__,_ y_)__;_ _}_
This is the same as:
_fn_ _tail__<__'__a__>__(__s__:_ _&__'__a_ _[__u8__]__)_ -> _&__'__a_ _[__u8__]_ _{_ _&_s_[__1_.._]_ _}_
This is legal:
_fn_ _main__(__)_ _{_ _let_ y = _{_ _let_ x = _&__[__1__,_ _2__,_ _3__,_ _4__,_ _5__]__;_ _tail__(_x_)_ _}__;_ _println__!__(__"y = {:?}"__,_ y_)__;_ _}_
…but only because [1, 2, 3, 4, 5] is a 'static array.
So, this is illegal:
_fn_ _main__(__)_ _{_ _let_ y = _{_ _let_ v = _vec__!__[__1__,_ _2__,_ _3__,_ _4__,_ _5__]__;_ _tail__(__&_v_)_ _// error: `v` does not live long enough_ _}__;_ _println__!__(__"y = {:?}"__,_ y_)__;_ _}_
…because a vector is heap-allocated, and it has a non-'static lifetime.
[
String slices (&str)
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#string-slices-str)
&str values are really slices.
_fn_ _file_ext__(__name__:_ _&__str__)_ -> _Option__<__&__str__>_ _{_ _// this does not create a new string - it returns_ _// a slice of the argument._ name_.__split__(__"."__)__.__last__(__)_ _}_ _fn_ _main__(__)_ _{_ _let_ name = _"Read me. Or don't.txt"__;_ _if_ _let_ Some_(_ext_)_ = _file_ext__(_name_)_ _{_ _println__!__(__"file extension: {}"__,_ ext_)__;_ _}_ _else_ _{_ _println__!__(__"no file extension"__)__;_ _}_ _}_
…so the borrow rules apply here too:
_fn_ _main__(__)_ _{_ _let_ ext = _{_ _let_ name = _String__::__from__(__"Read me. Or don't.txt"__)__;_ _file_ext__(__&_name_)__.__unwrap_or__(__""__)_ _// error: `name` does not live long enough_ _}__;_ _println__!__(__"extension: {:?}"__,_ ext_)__;_ _}_
[
Fallible functions (Result<T, E>)
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#fallible-functions-result-t-e)
Functions that can fail typically return a Result:
_fn_ _main__(__)_ _{_ _let_ s = std_::_str_::__from_utf8__(__&__[__240__,_ _159__,_ _141__,_ _137__]__)__;_ _println__!__(__"{:?}"__,_ s_)__;_ _// prints: Ok("🍉")_ _let_ s = std_::_str_::__from_utf8__(__&__[__195__,_ _40__]__)__;_ _println__!__(__"{:?}"__,_ s_)__;_ _// prints: Err(Utf8Error { valid_up_to: 0, error_len: Some(1) })_ _}_
If you want to panic in case of failure, you can .unwrap():
_fn_ _main__(__)_ _{_ _let_ s = std_::_str_::__from_utf8__(__&__[__240__,_ _159__,_ _141__,_ _137__]__)__.__unwrap__(__)__;_ _println__!__(__"{:?}"__,_ s_)__;_ _// prints: "🍉"_ _let_ s = std_::_str_::__from_utf8__(__&__[__195__,_ _40__]__)__.__unwrap__(__)__;_ _// prints: thread 'main' panicked at 'called `Result::unwrap()`_ _// on an `Err` value: Utf8Error { valid_up_to: 0, error_len: Some(1) }',_ _// src/libcore/result.rs:1165:5_ _}_
Or .expect(), for a custom message:
_fn_ _main__(__)_ _{_ _let_ s = std_::_str_::__from_utf8__(__&__[__195__,_ _40__]__)__.__expect__(__"valid utf-8"__)__;_ _// prints: thread 'main' panicked at 'valid utf-8: Utf8Error_ _// { valid_up_to: 0, error_len: Some(1) }', src/libcore/result.rs:1165:5_ _}_
Or, you can match:
_fn_ _main__(__)_ _{_ _match_ std_::_str_::__from_utf8__(__&__[__240__,_ _159__,_ _141__,_ _137__]__)_ _{_ Ok_(_s_)_ => _println__!__(__"{}"__,_ s_)__,_ Err_(_e_)_ => _panic__!__(_e_)__,_ _}_ _// prints 🍉_ _}_
Or you can if let:
_fn_ _main__(__)_ _{_ _if_ _let_ Ok_(_s_)_ = std_::_str_::__from_utf8__(__&__[__240__,_ _159__,_ _141__,_ _137__]__)_ _{_ _println__!__(__"{}"__,_ s_)__;_ _}_ _// prints 🍉_ _}_
Or you can bubble up the error:
_fn_ _main__(__)_ -> _Result__<__(__)__,_ std_::_str_::__Utf8Error__>_ _{_ _match_ std_::_str_::__from_utf8__(__&__[__240__,_ _159__,_ _141__,_ _137__]__)_ _{_ Ok_(_s_)_ => _println__!__(__"{}"__,_ s_)__,_ Err_(_e_)_ => _return_ _Err__(_e_)__,_ _}_ _Ok__(__(__)__)_ _}_
Or you can use ? to do it the concise way:
_fn_ _main__(__)_ -> _Result__<__(__)__,_ std_::_str_::__Utf8Error__>_ _{_ _let_ s = std_::_str_::__from_utf8__(__&__[__240__,_ _159__,_ _141__,_ _137__]__)_?_;_ _println__!__(__"{}"__,_ s_)__;_ _Ok__(__(__)__)_ _}_
[
Dereferencing
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#dereferencing)
The * operator can be used to dereference, but you don’t need to do that to access fields or call methods:
_struct_ _Point_ _{_ _x__:_ _f64__,_ _y__:_ _f64__,_ _}_ _fn_ _main__(__)_ _{_ _let_ p = _Point_ _{_ _x__:_ _1.0__,_ _y__:_ _3.0_ _}__;_ _let_ p_ref = _&_p_;_ _println__!__(__"({}, {})"__,_ p_ref_._x_,_ p_ref_._y_)__;_ _}_ _// prints `(1, 3)`_
And you can only do it if the type is Copy:
_struct_ _Point_ _{_ _x__:_ _f64__,_ _y__:_ _f64__,_ _}_ _fn_ _negate__(__p__:_ _Point__)_ -> _Point_ _{_ _Point_ _{_ _x__:_ -p_.__x__,_ _y__:_ -p_.__y__,_ _}_ _}_ _fn_ _main__(__)_ _{_ _let_ p = _Point_ _{_ _x__:_ _1.0__,_ _y__:_ _3.0_ _}__;_ _let_ p_ref = _&_p_;_ _negate__(__*_p_ref_)__;_ _// error: cannot move out of `*p_ref` which is behind a shared reference_ _}_
_// now `Point` is `Copy`_ _#_[_derive_(_Clone_,_ Copy_)__]__ _struct_ _Point_ _{_ _x__:_ _f64__,_ _y__:_ _f64__,_ _}_ _fn_ _negate__(__p__:_ _Point__)_ -> _Point_ _{_ _Point_ _{_ _x__:_ -p_.__x__,_ _y__:_ -p_.__y__,_ _}_ _}_ _fn_ _main__(__)_ _{_ _let_ p = _Point_ _{_ _x__:_ _1.0__,_ _y__:_ _3.0_ _}__;_ _let_ p_ref = _&_p_;_ _negate__(__*_p_ref_)__;_ _// ...and now this works_ _}_
[
Function types, closures
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#function-types-closures)
Closures are just functions of type Fn, FnMut or FnOnce with some captured context.
Their parameters are a comma-separated list of names within a pair of pipes (|). They don’t need curly braces, unless you want to have multiple statements.
_fn_ _for_each_planet__<__F__>__(__f__:_ _F__)_ _where_ _F__:_ _Fn__(__&__'__static_ _str__)_ _{_ _f__(__"Earth"__)__;_ _f__(__"Mars"__)__;_ _f__(__"Jupiter"__)__;_ _}_ _fn_ _main__(__)_ _{_ _for_each_planet__(_|planet| _println__!__(__"Hello, {}"__,_ planet_)__)__;_ _}_ _// prints:_ _// Hello, Earth_ _// Hello, Mars_ _// Hello, Jupiter_
The borrow rules apply to them too:
_fn_ _for_each_planet__<__F__>__(__f__:_ _F__)_ _where_ _F__:_ _Fn__(__&__'__static_ _str__)_ _{_ _f__(__"Earth"__)__;_ _f__(__"Mars"__)__;_ _f__(__"Jupiter"__)__;_ _}_ _fn_ _main__(__)_ _{_ _let_ greeting = _String__::__from__(__"Good to see you"__)__;_ _for_each_planet__(_|planet| _println__!__(__"{}, {}"__,_ greeting_,_ planet_)__)__;_ _// our closure borrows `greeting`, so it cannot outlive it_ _}_
For example, this would not work:
_fn_ _for_each_planet__<__F__>__(__f__:_ _F__)_ _where_ _F__:_ _Fn__(__&__'__static_ _str__)_ + _'__static_ _// `F` must now have "'static" lifetime_ _{_ _f__(__"Earth"__)__;_ _f__(__"Mars"__)__;_ _f__(__"Jupiter"__)__;_ _}_ _fn_ _main__(__)_ _{_ _let_ greeting = _String__::__from__(__"Good to see you"__)__;_ _for_each_planet__(_|planet| _println__!__(__"{}, {}"__,_ greeting_,_ planet_)__)__;_ _// error: closure may outlive the current function, but it borrows_ _// `greeting`, which is owned by the current function_ _}_
But this would:
_fn_ _main__(__)_ _{_ _let_ greeting = _String__::__from__(__"You're doing great"__)__;_ _for_each_planet__(__move_ |planet| _println__!__(__"{}, {}"__,_ greeting_,_ planet_)__)__;_ _// `greeting` is no longer borrowed, it is *moved* into_ _// the closure._ _}_
[
FnMut and borrowing rules
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#fnmut-and-borrowing-rules)
An FnMut needs to be mutably borrowed to be called, so it can only be called once at a time.
This is legal:
_fn_ _foobar__<__F__>__(__f__:_ _F__)_ _where_ _F__:_ _Fn__(__i32__)_ -> _i32_ _{_ _println__!__(__"{}"__,_ f_(_f_(__2__)__)__)__;_ _}_ _fn_ _main__(__)_ _{_ _foobar__(_|x| x _*_ _2__)__;_ _}_ _// output: 8_
This isn’t:
_fn_ _foobar__<__F__>__(__mut_ _f__:_ _F__)_ _where_ _F__:_ _FnMut__(__i32__)_ -> _i32_ _{_ _println__!__(__"{}"__,_ f_(_f_(__2__)__)__)__;_ _// error: cannot borrow `f` as mutable more than once at a time_ _}_ _fn_ _main__(__)_ _{_ _foobar__(_|x| x _*_ _2__)__;_ _}_
This is legal again:
_fn_ _foobar__<__F__>__(__mut_ _f__:_ _F__)_ _where_ _F__:_ _FnMut__(__i32__)_ -> _i32_ _{_ _let_ tmp = _f__(__2__)__;_ _println__!__(__"{}"__,_ f_(_tmp_)__)__;_ _}_ _fn_ _main__(__)_ _{_ _foobar__(_|x| x _*_ _2__)__;_ _}_ _// output: 8_
FnMut exists because some closures mutably borrow local variables:
_fn_ _foobar__<__F__>__(__mut_ _f__:_ _F__)_ _where_ _F__:_ _FnMut__(__i32__)_ -> _i32_ _{_ _let_ tmp = _f__(__2__)__;_ _println__!__(__"{}"__,_ f_(_tmp_)__)__;_ _}_ _fn_ _main__(__)_ _{_ _let_ _mut_ acc = _2__;_ _foobar__(_|x| _{_ acc += _1__;_ x _*_ acc _}__)__;_ _}_ _// output: 24_
Those closures cannot be passed to functions expecting Fn:
_fn_ _foobar__<__F__>__(__f__:_ _F__)_ _where_ _F__:_ _Fn__(__i32__)_ -> _i32_ _{_ _println__!__(__"{}"__,_ f_(_f_(__2__)__)__)__;_ _}_ _fn_ _main__(__)_ _{_ _let_ _mut_ acc = _2__;_ _foobar__(_|x| _{_ acc += _1__;_ _// error: cannot assign to `acc`, as it is a_ _// captured variable in a `Fn` closure._ _// the compiler suggests "changing foobar_ _// to accept closures that implement `FnMut`"_ x _*_ acc _}__)__;_ _}_
FnOnce closures can only be called once. They exist because some closure move out variables that have been moved when captured:
_fn_ _foobar__<__F__>__(__f__:_ _F__)_ _where_ _F__:_ _FnOnce__(__)_ -> _String_ _{_ _println__!__(__"{}"__,_ f_(__)__)__;_ _}_ _fn_ _main__(__)_ _{_ _let_ s = _String__::__from__(__"alright"__)__;_ _foobar__(__move_ || s_)__;_ _// `s` was moved into our closure, and our_ _// closures moves it to the caller by returning_ _// it. Remember that `String` is not `Copy`._ _}_
This is enforced naturally, as FnOnce closures need to be moved in order to be called.
So, for example, this is illegal:
_fn_ _foobar__<__F__>__(__f__:_ _F__)_ _where_ _F__:_ _FnOnce__(__)_ -> _String_ _{_ _println__!__(__"{}"__,_ f_(__)__)__;_ _println__!__(__"{}"__,_ f_(__)__)__;_ _// error: use of moved value: `f`_ _}_
And, if you need convincing that our closure does move s, this is illegal too:
_fn_ _main__(__)_ _{_ _let_ s = _String__::__from__(__"alright"__)__;_ _foobar__(__move_ || s_)__;_ _foobar__(__move_ || s_)__;_ _// use of moved value: `s`_ _}_
But this is fine:
_fn_ _main__(__)_ _{_ _let_ s = _String__::__from__(__"alright"__)__;_ _foobar__(_|| s_.__clone__(__)__)__;_ _foobar__(_|| s_.__clone__(__)__)__;_ _}_
Here’s a closure with two arguments:
_fn_ _foobar__<__F__>__(__x__:_ _i32__,_ _y__:_ _i32__,_ _is_greater__:_ _F__)_ _where_ _F__:_ _Fn__(__i32__,_ _i32__)_ -> _bool_ _{_ _let_ _(_greater_,_ smaller_)_ = _if_ _is_greater__(_x_,_ y_)_ _{_ _(_x_,_ y_)_ _}_ _else_ _{_ _(_y_,_ x_)_ _}__;_ _println__!__(__"{} is greater than {}"__,_ greater_,_ smaller_)__;_ _}_ _fn_ _main__(__)_ _{_ _foobar__(__32__,_ _64__,_ |x_,_ y| x > y_)__;_ _}_
Here’s a closure ignoring both its arguments:
_fn_ _main__(__)_ _{_ _foobar__(__32__,_ _64__,_ |__,_ _| _panic__!__(__"Comparing is futile!"__)__)__;_ _}_
Here’s a slightly worrying closure:
_fn_ _countdown__<__F__>__(__count__:_ _usize__,_ _tick__:_ _F__)_ _where_ _F__:_ _Fn__(__usize__)_ _{_ _for_ i _in_ _(__1_..=count_)__.__rev__(__)_ _{_ _tick__(_i_)__;_ _}_ _}_ _fn_ _main__(__)_ _{_ _countdown__(__3__,_ |i| _println__!__(__"tick {}..."__,_ i_)__)__;_ _}_ _// output:_ _// tick 3..._ _// tick 2..._ _// tick 1..._
[
The toilet closure
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#the-toilet-closure)
And here’s a toilet closure:
_fn_ _main__(__)_ _{_ _countdown__(__3__,_ |_| _(__)__)__;_ _}_
It’s called that because |_| () looks like a toilet.
[
Loops, iterators
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#loops-iterators)
Anything that is iterable can be used in a for in loop.
We’ve just seen a range being used, but it also works with a Vec:
_fn_ _main__(__)_ _{_ _for_ i _in_ _vec__!__[__52__,_ _49__,_ _21__]_ _{_ _println__!__(__"I like the number {}"__,_ i_)__;_ _}_ _}_
Or a slice:
_fn_ _main__(__)_ _{_ _for_ i _in_ _&__[__52__,_ _49__,_ _21__]_ _{_ _println__!__(__"I like the number {}"__,_ i_)__;_ _}_ _}_ _// output:_ _// I like the number 52_ _// I like the number 49_ _// I like the number 21_
Or an actual iterator:
_fn_ _main__(__)_ _{_ _// note: `&str` also has a `.bytes()` iterator._ _// Rust's `char` type is a "Unicode scalar value"_ _for_ c _in_ _"rust"__.__chars__(__)_ _{_ _println__!__(__"Give me a {}"__,_ c_)__;_ _}_ _}_ _// output:_ _// Give me a r_ _// Give me a u_ _// Give me a s_ _// Give me a t_
Even if the iterator items are filtered and mapped and flattened:
_fn_ _main__(__)_ _{_ _for_ c _in_ _"SuRPRISE INbOUND"_ _.__chars__(__)_ _.__filter__(_|c| c_.__is_lowercase__(__)__)_ _.__flat_map__(_|c| c_.__to_uppercase__(__)__)_ _{_ _print__!__(__"{}"__,_ c_)__;_ _}_ _println__!__(__)__;_ _}_ _// output: UB_
[
Returning closures
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#returning-closures)
You can return a closure from a function:
_fn_ _make_tester__(__answer__:_ _String__)_ -> _impl_ _Fn__(__&__str__)_ -> _bool_ _{_ _move_ |challenge| _{_ challenge == answer _}_ _}_ _fn_ _main__(__)_ _{_ _// you can use `.into()` to perform conversions_ _// between various types, here `&'static str` and `String`_ _let_ test = _make_tester__(__"hunter2"__.__into__(__)__)__;_ _println__!__(__"{}"__,_ test_(__"******"__)__)__;_ _println__!__(__"{}"__,_ test_(__"hunter2"__)__)__;_ _}_
[
Capturing into a closure
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#capturing-into-a-closure)
You can even move a reference to some of a function’s arguments, into a closure it returns:
_fn_ _make_tester__<__'__a__>__(__answer__:_ _&__'__a_ _str__)_ -> _impl_ _Fn__(__&__str__)_ -> _bool_ + _'__a_ _{_ _move_ |challenge| _{_ challenge == answer _}_ _}_ _fn_ _main__(__)_ _{_ _let_ test = _make_tester__(__"hunter2"__)__;_ _println__!__(__"{}"__,_ test_(__"*******"__)__)__;_ _println__!__(__"{}"__,_ test_(__"hunter2"__)__)__;_ _}_ _// output:_ _// false_ _// true_
Or, with elided lifetimes:
_fn_ _make_tester__(__answer__:_ _&__str__)_ -> _impl_ _Fn__(__&__str__)_ -> _bool_ + _'____ _{_ _move_ |challenge| _{_ challenge == answer _}_ _}_
[
Conclusion
](https://fasterthanli.me/articles/a-half-hour-to-learn-rust#conclusion)
And with that, we hit the 30-minute estimated reading time mark, and you should be able to read most of the Rust code you find online.
Writing Rust is a very different experience from reading Rust. On one hand, you’re not reading the solution to a problem, you’re actually solving it. On the other hand, the Rust compiler helps out a lot.
The Rust compiler has high-quality diagnostics (which include suggestions) for all the mistakes featured in this article.
And when there’s a hint missing, the compiler team is not afraid to add it.
For more Rust material, you may want to check out:
I also blog about Rust and post a lot about Rust on Mastodon and Twitter a lot, so if you liked this article, you know what to do!
Have fun!