iris-aiandClaude Opus 5
60367d806e
`Holds::through` inverts `px + rel * box`, and allowed three half steps either side: one for that multiply's rounding and two for the difference between a length composed down the chain and the same length measured against the window. The whole of a box has no multiply in it -- `rel` is one and taking the pixels off again is exact -- so the first half step was being allowed for a rounding that did not happen, and it compounded: a chain of widgets each taking the whole of its parent grew the interval half a step a level. Traced while making the multiply truncate, where the same compounding moved the interval off the box the drawing was made in and fired the `Holds` assertion in eleven generated cases. A range wider than what a drawing holds for is one that admits reusing it where it does not hold, so this is the unsound direction to be loose in. Checked: fmt, clippy, 80 suite tests and 16 core unit tests, the release oracle at 100 seeds, all fifteen shrinker cases at 400 seeds of depth 5 (seed 288 on `region-node` still failing and unchanged by this), and `tabs`, `view`, `minimal`, `text`, `random` plus the tab replay byte-identical at 1920x1200. 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