Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clean up Selector_List::operator== #2739

Merged
merged 2 commits into from
Nov 21, 2018
Merged

Conversation

glebm
Copy link
Contributor

@glebm glebm commented Nov 18, 2018

Implements equality for selector lists in a cleaner and more efficient manner.

The previous version checked for nulls in the list. This one does not, because there shouldn't be any nulls in there and we don't want to mask the underlying problem if there are.

Related issue: #2666 (likely fixed by this change but I haven't verified).

Implements equality for selector lists in a cleaner and more efficient manner.

Related issue: sass#2666 (likely fixed by this change but I haven't verified).
@xzyfer xzyfer merged commit 122d9f3 into sass:master Nov 21, 2018
@xzyfer xzyfer self-assigned this Nov 21, 2018
@glebm glebm deleted the selector-list-eq branch November 21, 2018 12:58
glebm added a commit to glebm/libsass that referenced this pull request Nov 25, 2018
Implements equality for `Compound_Selector` in a cleaner and more efficient manner.
Similar change for `Selector_List`: sass#2739

This does not fix the stack overflow reported in sass#2667, though it does
change its location (because we no longer clone any nodes in `operator==`).
glebm added a commit to glebm/libsass that referenced this pull request Nov 26, 2018
Implements equality for `Compound_Selector` in a cleaner and more efficient manner.
Similar change for `Selector_List`: sass#2739

This does not fix the stack overflow reported in sass#2667, though it does
change its location (because we no longer clone any nodes in `operator==`).
xzyfer pushed a commit that referenced this pull request Nov 26, 2018
Implements equality for `Compound_Selector` in a cleaner and more efficient manner.
Similar change for `Selector_List`: #2739

This does not fix the stack overflow reported in #2667, though it does
change its location (because we no longer clone any nodes in `operator==`).
@glebm glebm mentioned this pull request Nov 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants