Imbris

FWIW point 1 can probably be addressed via using `hashbrown` with [HashMap::entry_ref](https://docs.rs/hashbrown/0.14.0/hashbrown/struct.HashMap.html#method.entry_ref) + [Equivalent](https://docs.rs/hashbrown/0.14.0/hashbrown/trait.Equivalent.html).

I've seen cases in `iced` text layout that the proposed `SizeConstraint` doesn't cover (afaict): 1. A finite maximum width is specified but the size of the box shrinks to the...

I somewhat feel like needing to cover all these behaviors (with output size and alignment) is a motivation for having a separate measurement operation that doesn't interact with alignment at...

> If the goal is simply to measure the text's width for UI layout purposes, then (1) there will be some maximum width above which the exact result doesn't matter...

I've written up a pseudo-RFC with a potential API for measurement (where using `f32::MAX` will always work) as well as reusing work between measurement and final layout. I think it...

I just encountered a bug in my macro code where I assumed the `WhereClause` would be included and got errors that were difficult to track back to this. It's a...

> Closing this issue as the llvm coverage backend is now released as an alternative and there haven't been any updates here in over a year (as always feel free...

My case is that we use `panic = "abort"` for our release binaries. And that can potentially affect runtime performance. So being able to toggle this on for benchmarks would...

Code paths can also be conditionally included based on the panic setting, e.g. with `#[cfg(panic = "unwind")]`. Which could impact runtime performance in addition to the difference introduced by the...

``` stderr: error: line 127: Case construct that targets '74[%74]' has invalid branch to block '55[%55]' (not another case construct, corresponding merge, outer loop merge or outer loop continue) %74...