Reason about nested free variables that appear in a function signature #5795
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.
Reason about nested free variables that appear in a function
signature. In a nutshell, the idea is to (1) report an error if, for
a region pointer
'a T
, the lifetime'a
is longer than anylifetimes that appear in
T
(in other words, if a borrowed pointeroutlives any portion of its contents) and then (2) use this to assume
that in a function like
fn(self: &'a &'b T)
, the relationship'a <= 'b
holds. This is needed for #5656. Fixes #5728.r? @pcwalton