lint: use Keyify internally #691
Open
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.
There are 4 intersect helpers that could benefit from using the existing
Keyify
helper internally.This is a question I have quite often whilst working on iterators support - when is it appropriate to use another helper and when is it better to implement from scratch?
There are lots of places where simple helpers like
Empty
orMap
or evenTernary
could be used. What about related helpers like likeCount
usingCountBy
internally, etc?