[TASK] Deprecate greedy calculation of selector specificity #1018
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
oliverklee
added this to the
9.0.0: Drop support for PHP < 7.2 and clean up things milestone
oliverklee
force-pushed
the
task/deprecate/selector-specificity
branch
from
69278ac to
b2c5b62
Compare
This constructor parameter is not used, and having the specificity calculation always done lazily is not a problem.
oliverklee
force-pushed
the
task/deprecate/selector-specificity
branch
from
b2c5b62 to
b2e2267
Compare
JakeQZ
approved these changes
Feb 27, 2025
Collaborator
JakeQZ
left a comment
JakeQZ
left a comment
There was a problem hiding this comment.
Indeed, it can be done on first-time access without loss of performance.
oliverklee
added a commit
that referenced
this pull request
Feb 27, 2025
This constructor parameter is not used, and having the specificity calculation always done lazily is not a problem. This is the V8.x backport of #1018.
JakeQZ
pushed a commit
that referenced
this pull request
Feb 27, 2025
This constructor parameter will no longer be used; having the specificity calculation always done lazily is not a problem. This is the V8.x backport of #1018.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This constructor parameter is not used, and having the specificity calculation always done lazily is not a problem.