Skip to content

Roadmap

Level: reference · for anyone choosing what to write next

Chapter 01 — Time and benchmarking

Six lessons are written and six are outlines. Graduate the outlines in this order; each leans on the one before it:

  1. What happens in now() — its central evidence (strace showing no system call) exists only on Linux, so it will be a dated fence rather than an answer key.
  2. The cost of asking the time — first measurements are already on Timing a block of code.
  3. Reading the cycle counter — rdtsc is x86-64 while the macOS CI runner is arm64, so the example must cover both architectures or live in a dated fence.
  4. The branch predictor learns your benchmark
  5. The cache changes the answer
  6. One number is not a measurement

After this chapter

Not yet folders — a folder name is a permanent URL, so a chapter gets one when its first page is written. Candidates, each chosen because a sibling library already holds the other half:

  • Undefined behaviour — the Rust library's C and C++ ↗ section runs nine bugs in C and shows Rust refusing each one; what C++ itself offers against them belongs here.
  • Text — std::string holds bytes; the Encodings library ↗ already covers what the bytes mean.
  • Ownership — unique_ptr, moves and RAII: the C++ that the Rust library's ownership rules reply to.