9f825ed6fbd7c85b7147b2f8a1724e676c839cc1
`5f16617` carries the composed box down the draw instead of walking back up for it, which made exact composition a 3.6%/3.3% speedup rather than a cost. The numbers are in "Performance" and the i64 item. And seed 220 is diagnosed rather than left as a seed. `offered_region` composes a widget's offer through its ancestors' offers except where the parent is a region node, where it falls back to the node's **placed** box. `Scroll` is where placed and offered differ -- it offers its content the viewport and places it in a box as long as the content -- so the offer becomes a function of the answer being re-derived and the old answer confirms itself. It is the fourth defect this session to come down to the offer against the placed box. The write-up has the trace both ways, the fact that each child order settles to its own fixed point so the tree is not unsettled, that marking everything dirty converges warm onto cold, and the coordinate-frame problem that makes the two plausible fixes awkward -- `offer` is in the parent widget's frame and `region` in the parent node's, so neither answers "was this placed where it was offered" alone. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Languages
Rust
53%
Kotlin
44.4%
Shell
2.6%