Repository navigation
Remove unnecesary uses of the 'current_func' field, replacing it with a call to function. - #722
Merged
Merged
Conversation
… a call to function.
antoyo
approved these changes
Jun 26, 2025
antoyo
left a comment
antoyo
left a comment
Contributor
There was a problem hiding this comment.
Nice improvement!
Thanks!
Contributor
|
Thanks for your contribution! |
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.
All uses of the
current_funcfield ofContextinBuildercan be safely replaced withBuilder::current_func. This is done in preparation for removal of that field.Only one use of
current_funcremains - withinconst_undef, which is a function ofContext, and notBuilder.