cassowary-rs
cassowary-rs copied to clipboard
Add Variable::from_usize
Rationale: I have a unique reproducible way of generating keys per variable; using that saves me from creating a Variable → key map.
Oh, look at that. You did!
Yes, I did. This crate appears unmaintained. For my use-case, I'll probably move kas away from Cassowary anyway because it is inefficient and hard to debug.
What will you use instead? Are the inefficiencies unable to be overcome with some profiling?
I'm mostly done with replacement code for my case which isn't quite as flexible but good enough and a lot simpler overall. I'll link to it when I'm done.
Inefficiencies are mostly because of the number of allocations this lib does, I think. Haven't looked into it much and it may still be good enough.
What will you use instead?
My replacement code is mostly done now, and very specific to my use-case (widget placement). See:
The latter is the heart of this system: lots of code injected per widget (I am hoping this doesn't cause issues when scaling to complex UIs; it also needs adjustment to handle dynamic content).