Day 24 of 30 · First contribution
Locate the smallest responsible code path
- Time
- About 150 minutes: 40 reading, 80 lab, 20 testing, 10 notes.
Toolchain: current-main build
Use build/bin/clang++ and build/bin/llvm-lit from your llvm-main checkout, not whichever clang++ is first on PATH. Reproduce upstream behavior on current main and record the commit SHA. Setup guide
Learn
- A hypothesis before a patch.
Read Reading
- Your llvm-project checkout
The relevant implementation and two adjacent tests · 40 min
Reading budgets cover selected sections, not whole chapters. Link to the book; this site does not reproduce it.
Build Build or investigate
- Trace the reproducer to one checking or reporting path.
- Write a proposed change and the cases it might affect.
- If the issue needs unfamiliar template machinery or a large redesign, choose a smaller fallback now.
- Ask a focused question only after recording your investigation.
Done when
A patch hypothesis, candidate files and a boundary-case list; no speculative broad refactor.
Recall question
What counterexample would show that your proposed fix is too broad?
Completion checks
Progress tracking needs JavaScript. The lesson above is complete without it.
Notes
Saved only in this browser. Keep it short enough to finish in ten minutes; none of the prompts are required. All notes, export and import