Rust Core
The compiler's side of the argument, made explicit. A lifetime constrains how long a borrow may be used rather than naming a span of time, an iterator chain does nothing at all until something consumes it, and a trait bound is the only thing a generic function is allowed to assume.
Who it is for
Works in it, has gaps.
The behaviour people get wrong after they are already productive in the language.
You will get the most out of it if you have written Rust recently enough to read it without effort, and have been surprised by it at least once. If you are picking the language up for the first time, start with Rust Essentials and come back to this one.
How long it takes
90 graded questions at roughly 45 seconds each is about 68 minutes of answering in total.
At the default five questions a day, and because the session mixes in your other courses, expect around 18 days — call it 3 weeks — to see everything once, plus a few weeks of thinning reviews after that before it is all mastered.
A question is mastered on the third correct answer, once the gap between reviews has grown past a week — so a course cannot be finished in a weekend however long you sit with it.
Question mix
- 60 multiple choice
- 10 concept cards
- 10 predict the output
- 10 put it in order
- 10 matching questions
Syllabus
What you will be asked about
-
01
Lifetimes
Read a lifetime annotation as a constraint relating two borrows rather than a claim about how long a value lives.
-
02
Structs & Enums
Give a struct or enum behaviour with an impl block, and choose between self, &self and &mut self.
-
03
Traits
Define a trait with a default method, implement it for a type, and say what having the trait in scope changes.
-
04
Generics & Bounds
State what a generic function may assume about its type parameter, and read a bound as the list of those assumptions.
-
05
Result & ?
Return a Result and use ? to hand a failure back to the caller instead of unwrapping it.
-
06
Lazy Iterators
Say which parts of an iterator chain have run, and identify the call that finally drives it.
-
07
Closures
Tell Fn, FnMut and FnOnce apart by what the closure does to the values it captured.
-
08
Deref Coercion
Explain why a &String is accepted where a &str is wanted, and name the places the coercion does not reach.
-
09
Guards & Bindings
Add a guard or a binding to a pattern and predict which arm a value reaches.
-
10
Vec Growth & Indexing
Predict what push, indexing and removal do to a Vec, and why a live borrow into one blocks them.
8 more topics, and all 90 questions
Rust Core is a Pro course. One subscription opens it and every other course in the catalogue, including the ones still being written.
A question from this course
Lifetimes
What happens here?
fn pick() -> &str {
let s = String::from("hi");
&s
}
fn main() {
println!("{}", pick());
}Show the answer
B It does not compile: the return type needs a lifetime, and there is no input for it to come from
With no reference parameter there is nothing for the result to borrow from, so elision has no candidate and rustc asks for a lifetime it could never satisfy. You may have expected the dangling pointer to slip through and misbehave at run time, which is exactly what this rule exists to prevent. Returning the String itself is the fix; borrowing a local never can be.
The rest of the track
Rust at every depth
Rust Essentials
The model underneath the syntax. Assigning a String to a second name moves it and the first name stops working, while an i32 is simply copied; borrowing, Option and exhaustive match are the same compiler insisting you say what happens in every case.
Rust Data & Collections
The containers people reach for daily and the places they bite: indexing that panics where get() hands back None, a borrow that freezes the Vec it came from, and an entry() call that writes when you only meant to read. Every snippet here runs, so the answers are what rustc really printed.
Rust Errors & Edge Cases
Failure as a value rather than an exception: Option where there is nothing to say and Result where there is, the ? operator and the From impl it quietly needs, custom error enums, Display against Debug, and the line between an error a caller can act on and a panic that ends the process. Every snippet here either runs or refuses to compile for a reason you can name.
Rust Standard Library
The parts of std that people reimplement by hand: the String and &str split, chars against bytes, the split and trim families, parse and the turbofish, the lazy iterator adaptors, collect into anything that implements FromIterator, the Option and Result combinators, the three sorts, and the Display against Debug distinction. Ten corners where a built-in already does the job and one behaviour in each is not what you assumed.
Rust Idioms & Pitfalls
Ten habits that compile and still mark the code as written by someone thinking in another language: the clone that silences the borrow checker, unwrap as punctuation, String parameters where a slice would do, index loops, a collect nobody reads, a five-line match that is one combinator, &Vec in a signature, lifetimes elision would have written, inherent methods that want to be trait impls, and drop misread. Each one is shown working, then shown costing something.
Rust Advanced
The type system and the borrow checker in earnest: elision that quietly ties a return to &self, two &mut borrows that look disjoint and are not, RefCell panicking at run time where the compiler would have refused. Every snippet here either compiles or fails to for a reason you can name.
Rust Performance
What a Rust program actually costs, read off the things you can observe: Vec::capacity, strong_count, size_of and the order drops run in. Every claim here is one the snippet proves, which is why none of them is a timing.
Rust Testing
What a Rust assertion actually claims, and where that claim is weaker than it looks. assert_eq! and its argument order, should_panic and its substring match, tests that return Result, cfg(test) modules against integration tests, doc tests, floats, and the difference between a failed assertion and a panic somewhere else.
Rust Interview Questions
The questions a Rust interview actually turns on: where a value's owner is at each line, why two borrows that look disjoint are not, and what a lifetime annotation promises and what it cannot. Ownership and moves, aliasing, lifetimes, String against &str, Vec against slices, Option and Result, traits and dispatch, monomorphisation, Rc and RefCell, and what makes a type safe to send between threads.
Start Rust Core
in tomorrow’s session.
Enrol and this course joins your daily five, mixed in with everything else you are studying — 90 questions spread over about 18 days rather than dropped on you at once.
Browse the catalogue