Add CollectionIndexOnNonIndexedSeq rule to Scapegoat#1
Closed
Add CollectionIndexOnNonIndexedSeq rule to Scapegoat#1
Conversation
Owner
Author
|
Upstream PR: scapegoat-scala#158 |
0a1bb31 to
36ad93e
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.
Inspired by https://twitter.com/jshrsn/status/865677863646658560, this patch adds a new
IndexingOnANonIndexedSeqrule which raises a warning when we see code which indexes on aSeqwhich isn't known to be anIndexedSeqsubtype. The goal here is to make it easier to prevent cases where someone writes anO(n^2)loop by accident.This rule should have prevented the following Spark bugs:
For comparision, here's the same rule implemented in
linter: JoshRosen/linter#1