Fix file pointer errors around >= and <= tokens
#341
Merged
Conversation
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
fourls
deleted the
gte_tokens_are_the_bane_of_my_existence_and_must_be_expunged_from_this_plane
branch
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.
This PR fixes instances of
IllegalArgumentExceptionbeing raised by the CPD executor on lines that end with>=or<=,, caused by file pointer errors.>=and<=token positions were incorrect after token combination had occurred.The solution is to adjust the token
lineandcharPositionInLineas part of the combination step, where we previously only adjusted the token start/stop indices.