Closed nolanlawson closed 4 years ago
Cuts down a bit of duplicated code.
FWIW I also tested if it made sense to cache the result of postcssSelectorParser(), but in our whole test suite, running in Chrome on my MacBook, it consumed a sum total of ~3ms. So I don't think it's really worth it.
postcssSelectorParser()
Cuts down a bit of duplicated code.
FWIW I also tested if it made sense to cache the result of
postcssSelectorParser()
, but in our whole test suite, running in Chrome on my MacBook, it consumed a sum total of ~3ms. So I don't think it's really worth it.