Categorically fix type issues with restore_on_out_of_scope #78460
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.
Summary
None
Purpose of change
Followup to #78452. Eliminate confusion and standardize on an untyped pattern for
restore_on_out_of_scope
. This categorically avoids issues with explicit typing that doesn't match the type of the variable, which then avoid incorrect behavior caused by compiler generated temporaries for conversions.Describe the solution
Automatically remove the explicit typing from all
restore_on_out_of_scope
in the repo with sed. Delete the constructor that accepts a non-T so future erroneous usage gets a compile error.Describe alternatives you've considered
Not.
Testing
CI.
Additional context