ParserBase: avoid copying around currentLiteral #15741
Merged
+8
−7
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
clonker
commented
Jan 20, 2025
| @@ -198,7 +198,7 @@ void ObjectParser::parseData(Object& _containingObject) | |||
| std::string ObjectParser::parseUniqueName(Object const* _containingObject) | |||
| { | |||
| expectToken(Token::StringLiteral, false); | |||
| auto const name = currentLiteral(); | |||
| std::string const name{currentLiteral()}; | |||
There was a problem hiding this comment.
Here storing an explicit copy is required as we advance before returning from the function.
There was a problem hiding this comment.
Since this is an issue, it may be worthwhile to document the lifetime of the string_view in the header (i.e. state that advance invalidates it there)?
1c760ae to
5389915
Compare
r0qs
reviewed
Jan 22, 2025
nikola-matic
approved these changes
Jan 29, 2025
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 is something that I randomly stumbled upon when looking at #15712.
The function
ParserBase::currentLiteral()is called very frequently, in particular also in a lookup-style (e.g.,m_dialect.findBuiltin(currentLiteral())). Currently, each invocation takes a full copy of the string value of whatever the scanner is pointing to.