chore(parser): use eat in a loop instead of recursing bump
#361
Conversation
This file contains 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
We're inside `bump_ignored()` here, and `bump()` calls `bump_ignored()` again internally. So this loop didn't really do a lot: we end up doing just one iteration in the loop and recursing into `bump_ignored()` again to eat the next token. Using `eat()` here is equivalent but without the recursion.
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.
A little simplification 😇
We're inside
bump_ignored()here, andbump()callsbump_ignored()again internally. So this loop didn't really do a lot: we end up doing just one iteration in the loop and recursing intobump_ignored()again to eat the next token.Using
eat()here is equivalent but without the recursion.