fix inTypeofContext
leaking after compiles
raises exception [backport:2.0]
#24152
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.
fixes #24150, refs #22022
An exception is raised in the
semExprWithType
call, which meansdec c.inTypeofContext
is never called, butcompiles
allows compilation to continue. This meansc.inTypeofContext
is left perpetually nonzero, which preventscompileTime
evaluation for the rest of the program.To fix this,
defer:
is used for thedec c.inTypeofContext
call, as is done forinstCounter
in other parts of the compiler.