Check if dropping an expression may have indirect side-effects #14594
+64
−5
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.
It is not enough to check if an expression type implements
Drop
to determine whether it can have a significant side-effect.Also, add tests for unchecked cases which were explicitly handled in the code, such as checking for side effect in a
struct
's fields, or in its base expression.Fix #14592
changelog: [
no_effect_underscore_binding
]: do not propose to remove the assignment of an object if dropping it might indirectly have a visible side effect