Use a separate LtrbRect type for render calculations #15112
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We are doing quite a lot of Union/Intersect/Intersects operations in the renderer and those operate with Left/Top/Right/Bottom properties.
Our Rect type doesn't store Right/Bottom and has Width/Height instead, so there are lots of conversions. Render frame went from 26.5ms to 25.0ms on a "lots of controls on a canvas" benchmark, so the perf gain is significant enough to justify having a separate type.