fix: More accurate lifetime bounds on scoped methods to allow valid code to compile #919
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.
Prior to this change, it was impossible to escape a value in
execute_scoped
that was created in an outer scope. This is because thefunction definition allowed for the outer and inner lifetimes to be entirely unrelated.
This is technically a breaking change, but in many cases the more strict bound will cause code to be more likely to compile.
The following code compiles after this change, but not before: