rule_order: merge a same-slot pair at a position between them - #216
Open
samoht wants to merge 2 commits into
Open
rule_order: merge a same-slot pair at a position between them#216samoht wants to merge 2 commits into
samoht wants to merge 2 commits into
Conversation
Expanding a selector list leaves two rules on one selector that neither endpoint can host: folding the earlier one forward passes a write that observes it, folding the later one back passes a different one. A position between the two is legal for both, since each then crosses a shorter interval, so a factored sheet reaches the shape an unfactored one starts from instead of canonicalising to a different one.
samoht
force-pushed
the
canon-remerge-after-expand
branch
from
July 29, 2026 22:37
bcb8957 to
dc8dde9
Compare
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
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.
expand_listssplits a selector-list rule into one rule per selector, which can leave two rules on a single selector that neither end of the pair can host: folding the earlier one forward passes a write that observes it, and folding the later one back passes a different one.coalescetested only those two endpoints, so it gave up while a position between them was legal for both, and a factored sheet canonicalised to a different shape from an unfactored one.--diff=canonicalthen reported the second rule's declarations as missing.On the tailwindcss.com comparison this closes eight phantom entries, the four
text-xs/Nand fourdrop-shadow-*rules, with no entry appearing that was not already reported before the change.