iris-aiandClaude Opus 5
5ed9e874a3
The shrinker's `reorder` case had two red seeds at depth 5, and neither was about reordering. A span asks whether anything is left over by comparing its box in pixels with what its fixed and relative children fill. Where the parent sized that box from this span's own answer those are the same number, and the box returns through the chain a few bits off, so 0.00003 px decided it: warm rounded under and left a leftover-only child undrawn, cold rounded over and drew it at zero length. Both are stable, and the pixels are the same either way, which is why nothing but the oracle could see it. The room to divide is `len * fixed - total.px`, and under `HOLDS_EPSILON_PX` of it is now none. That moves the boundary off the length boxes land on rather than making the comparison tolerant: the validity range is still split at the boundary exactly, as generated seed 16 requires, and what it gives up is a share of under a twentieth of a pixel. The same margin answers the `fixed == 0` arm, where the only room is what negative pixels leave. `tests/unsettled.rs` gets the six-widget tree, shrunk from 266. It needs the span above the one that divides: without a box composed through it both trees round the same way and the boundary is never crossed. Checked: fmt, clippy, 89 tests, 100 generated seeds agreeing in 68.5 s, and all five shrinker cases at 1000 seeds of depth 6 (159,024 widgets each). `tabs`, `view`, `minimal`, `text` and `random` render byte-identical at 1920x1200 against the same worktree without the change. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
iris
My experimental attempt at a rust ui library (also my first ui library).
It's currently designed around using retained data structures (widgets), rather than diffing generated trees from data like xilem or iced. This is an experiment and I'm not sure if it's a good idea or not.
Examples are in examples, eg. cargo run --example tabs.
Goals, in general order:
- does what I want it to (text, images, video, animations)
- very easy to use ignoring ergonomic ref counting
- reasonably fast / efficient (a lot faster than electron, save battery life, try to beat iced and xilem)
dev details
not targeting web rn cause wanna use actual nice gpu features & entire point of this is to make desktop apps / not need a web browser
general ideas trynna use rn / experiment with:
- retained mode
- specifically designed around wgpu so there's no translation
- postfix functions for most things to prevent unreadable indentation (going very well)
- events can be done directly where you draw the widgets
- almost no macros in user code & actual LSP typechecking (variadic generics if you can hear me please save us)
- relative anchor + absolute offset coord system (+ "rest" / leftover during widget layout)
- single threaded ui & pass context around to make non async usage straightforward (pretty unsure about this)
- widgets store outside of the actual rendering so they can be moved around and swapped easily (unsure about this but seems to work good for now)
under heavy initial development so not gonna try to explain status, maybe check TODO for that; sizable chance it gets a rewrite once I know everything I need and what seems to work best
it's called iris because it's the structure around what you actually want to display and colorful