Skip to content
← All tracks

The Expert Edge: Idiom, Review and Capstones

Rust

Write Rust a senior reviewer would sign off on, and reason honestly about what things cost. Multi-track capstones that need several earlier tracks at once.

This track is written for Rust, which isn't the mode you're browsing in.

0 / 11 solved · 3 articles
Continue →
  1. 1. Not solved yet. Enum state machines with data-carrying transitions
  2. 2. Not solved yet. Folding an AST: separating traversal from action
  3. 3. Not solved yet. A macro-generated FFI binding layer
  4. 4. Not solved yet. Build Rc<T> and RefCell<T> from scratch
  5. 5. Not solved yet. Capstone: an ownership-only job scheduler
  6. 6. Not solved yet. Capstone: build a thread pool
  7. 7. Not solved yet. Capstone: an async executor with a logical-time reactor
  8. 8. Not solved yet. Capstone: a fully-typed fallible parser
  9. 9. Not solved yet. Capstone: audit and repair an unsound abstraction
  10. 10. Zero-cost abstractions, examined Read
  11. 11. Not solved yet. Unsound API smells: the patterns that are always wrong
  12. 12. Not solved yet. Designing safe wrappers around unsafe FFI
  13. 13. The reviewer's idiom checklist Read
  14. 14. When not to use unsafe, and when not to use async Read

Check yourself

4 questions · one attempt each

These do not count toward finishing the track. They are here to catch the things that are easy to read past.

0 / 4

Which Fn trait does this closure implement, and why can it be called twice? 

let mut count = 0;
let mut inc = || { count += 1; };
inc();
inc();
Question 1 of 4