iris-aiandClaude Opus 5
99131940ab
A parent that sizes to a child offers it back the length it just reported, so a wrapping text was re-broken at exactly its own longest line. That is a knife edge: the length is composed back through the box chain, so it lands an ulp either side of where it started, and which side decides whether the longest line still fits. One side kept three lines at 167.41, the other took four at 163.49 -- from the same text in the same box, differing only in what the output size had been. A greedy break does not need recomputing there. Breaking at one width gives lines that each fit, none of which could have taken another word; at any narrower width down to the longest of them, every line still fits and none can take a word that did not fit in more room. So one break answers a whole interval, and the cache now hits across it rather than on the exact width. The tolerance is what makes it hold at the edge, which is the case that matters: sub-pixel, so no break it admits is one anybody could see. The generated sweep passes at depth 6, where it failed; the shrinking fuzzer agrees over 800 trees at depth 7 on all three scenarios, where two of them failed. `tests/unsettled.rs` is green, so the whole suite is. Depth 7 of the generated sweep still fails. 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