Optimise style comparison when computing damage #227
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.
Fixes #226
This implements three optimisations:
oldandnew&ComputedValuesareptr::eqthen diffing the styles is entirely skipped. This occurs when an element is restyled but none of the styles actually change.ptr::eqbefore diffing individual properties. If the structs areptr::eqthen no damage is generated from that struct.If ALL of the longhand properties in a style struct affect a given a property then we can also skip diffing individual properties in the case that the struct is notThis optimisation was removed because it may be possible (we are unsure) for style properties to be the same even if the pointers differ. And in that case this would like pessimise performance.ptr::eq. In that case damage is generated and we can return early with that result.Servo PR: servo/servo#39772
Generated code with this PR is: