Cascade
Rules fly in; you call the winner before the timer runs out. Repetition until the ordering is reflex rather than recall.
You have read the algorithm and you have stepped through the resolver. This is the part where it becomes fast enough to use while you are debugging something else.
Play until you can clear a round without consciously walking the four steps. That is the point at which cascade bugs stop costing you fifteen minutes each.
If you stall on a particular shape, layers, or important, or the inline-style case, go back to the resolver and step through that one specific configuration a few times, then come back.
Tiebreak
Predict which declaration survives when origin, layers, specificity and order disagree.
Play TiebreakYou should now be able to
- Call the winning declaration at speed
- Recognise the shape of each cascade step under time pressure
Loading…