ast/parser: avoid duplicate loc copies#8142
Merged
srenatus merged 1 commit intoopen-policy-agent:mainfrom Dec 19, 2025
Merged
Conversation
Those two changes share a location, and those are read-only, so there should be no need to create two separate copies via calling `p.s.Loc()`. Signed-off-by: Stephan Renatus <stephan.renatus@gmail.com>
✅ Deploy Preview for openpolicyagent ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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
2 participants
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.
Those two changes share a location, and those are read-only, so there should be no need to create two separate copies via calling
p.s.Loc().Not the answer to why parsing "every" allocates more when it doesn't contain a string literal, but fine. It should still be correct.