Fix #7011: check possibly side-effecting transform #7016
Merged
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.
The transform function in question can be overridden with a version
that produces side effects. If that is the case, and if the superclass
transform function is called from the overridden transform function,
the overridden transform function might be executed twice with all its
side effects. This commit makes sure the transform function is not
called twice on the same input. An example where it can go wrong is:
https://github.com/lampepfl/dotty/blob/9a4b7d39a595dba3c0baf340b0bf911844fcae69/compiler/src/dotty/tools/dotc/typer/Typer.scala#L1080-L1094
Here, the transform function performs the side effect of entering a symbol
into scope. Furthermore, if the symbol already exists in scope, it emits
an error. Hence, if we call this function twice on the same argument,
we are guaranteed to get an error.