-
Notifications
You must be signed in to change notification settings - Fork 12.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
introduce a fudge_regions_if_ok
to address false region edges
#37659
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,137 @@ | ||
// Copyright 2012-2015 The Rust Project Developers. See the COPYRIGHT | ||
// file at the top-level directory of this distribution and at | ||
// http://rust-lang.org/COPYRIGHT. | ||
// | ||
// Licensed under the Apache License, Version 2.0 <LICENSE-APACHE or | ||
// http://www.apache.org/licenses/LICENSE-2.0> or the MIT license | ||
// <LICENSE-MIT or http://opensource.org/licenses/MIT>, at your | ||
// option. This file may not be copied, modified, or distributed | ||
// except according to those terms. | ||
|
||
use ty::{self, TyCtxt}; | ||
use ty::fold::{TypeFoldable, TypeFolder}; | ||
|
||
use super::InferCtxt; | ||
use super::RegionVariableOrigin; | ||
|
||
impl<'a, 'gcx, 'tcx> InferCtxt<'a, 'gcx, 'tcx> { | ||
/// This rather funky routine is used while processing expected | ||
/// types. What happens here is that we want to propagate a | ||
/// coercion through the return type of a fn to its | ||
/// argument. Consider the type of `Option::Some`, which is | ||
/// basically `for<T> fn(T) -> Option<T>`. So if we have an | ||
/// expression `Some(&[1, 2, 3])`, and that has the expected type | ||
/// `Option<&[u32]>`, we would like to type check `&[1, 2, 3]` | ||
/// with the expectation of `&[u32]`. This will cause us to coerce | ||
/// from `&[u32; 3]` to `&[u32]` and make the users life more | ||
/// pleasant. | ||
/// | ||
/// The way we do this is using `fudge_regions_if_ok`. What the | ||
/// routine actually does is to start a snapshot and execute the | ||
/// closure `f`. In our example above, what this closure will do | ||
/// is to unify the expectation (`Option<&[u32]>`) with the actual | ||
/// return type (`Option<?T>`, where `?T` represents the variable | ||
/// instantiated for `T`). This will cause `?T` to be unified | ||
/// with `&?a [u32]`, where `?a` is a fresh lifetime variable. The | ||
/// input type (`?T`) is then returned by `f()`. | ||
/// | ||
/// At this point, `fudge_regions_if_ok` will normalize all type | ||
/// variables, converting `?T` to `&?a [u32]` and end the | ||
/// snapshot. The problem is that we can't just return this type | ||
/// out, because it references the region variable `?a`, and that | ||
/// region variable was popped when we popped the snapshot. | ||
/// | ||
/// So what we do is to keep a list (`region_vars`, in the code below) | ||
/// of region variables created during the snapshot (here, `?a`). We | ||
/// fold the return value and replace any such regions with a *new* | ||
/// region variable (e.g., `?b`) and return the result (`&?b [u32]`). | ||
/// This can then be used as the expectation for the fn argument. | ||
/// | ||
/// The important point here is that, for soundness purposes, the | ||
/// regions in question are not particularly important. We will | ||
/// use the expected types to guide coercions, but we will still | ||
/// type-check the resulting types from those coercions against | ||
/// the actual types (`?T`, `Option<?T`) -- and remember that | ||
/// after the snapshot is popped, the variable `?T` is no longer | ||
/// unified. | ||
/// | ||
/// Assumptions: | ||
/// - no new type variables are created during `f()` (asserted | ||
/// below); this simplifies our logic since we don't have to | ||
/// check for escaping type variables | ||
pub fn fudge_regions_if_ok<T, E, F>(&self, | ||
origin: &RegionVariableOrigin, | ||
f: F) -> Result<T, E> where | ||
F: FnOnce() -> Result<T, E>, | ||
T: TypeFoldable<'tcx>, | ||
{ | ||
let (region_vars, value) = self.probe(|snapshot| { | ||
let vars_at_start = self.type_variables.borrow().num_vars(); | ||
|
||
match f() { | ||
Ok(value) => { | ||
let value = self.resolve_type_vars_if_possible(&value); | ||
|
||
// At this point, `value` could in principle refer | ||
// to regions that have been created during the | ||
// snapshot (we assert below that `f()` does not | ||
// create any new type variables, so there | ||
// shouldn't be any of those). Once we exit | ||
// `probe()`, those are going to be popped, so we | ||
// will have to eliminate any references to them. | ||
|
||
assert_eq!(self.type_variables.borrow().num_vars(), vars_at_start, | ||
"type variables were created during fudge_regions_if_ok"); | ||
let region_vars = | ||
self.region_vars.vars_created_since_snapshot( | ||
&snapshot.region_vars_snapshot); | ||
|
||
Ok((region_vars, value)) | ||
} | ||
Err(e) => Err(e), | ||
} | ||
})?; | ||
|
||
// At this point, we need to replace any of the now-popped | ||
// region variables that appear in `value` with a fresh region | ||
// variable. We can't do this during the probe because they | ||
// would just get popped then too. =) | ||
|
||
// Micro-optimization: if no variables have been created, then | ||
// `value` can't refer to any of them. =) So we can just return it. | ||
if region_vars.is_empty() { | ||
return Ok(value); | ||
} | ||
|
||
let mut fudger = RegionFudger { | ||
infcx: self, | ||
region_vars: ®ion_vars, | ||
origin: origin | ||
}; | ||
|
||
Ok(value.fold_with(&mut fudger)) | ||
} | ||
} | ||
|
||
pub struct RegionFudger<'a, 'gcx: 'a+'tcx, 'tcx: 'a> { | ||
infcx: &'a InferCtxt<'a, 'gcx, 'tcx>, | ||
region_vars: &'a Vec<ty::RegionVid>, | ||
origin: &'a RegionVariableOrigin, | ||
} | ||
|
||
impl<'a, 'gcx, 'tcx> TypeFolder<'gcx, 'tcx> for RegionFudger<'a, 'gcx, 'tcx> { | ||
fn tcx<'b>(&'b self) -> TyCtxt<'b, 'gcx, 'tcx> { | ||
self.infcx.tcx | ||
} | ||
|
||
fn fold_region(&mut self, r: &'tcx ty::Region) -> &'tcx ty::Region { | ||
match *r { | ||
ty::ReVar(v) if self.region_vars.contains(&v) => { | ||
self.infcx.next_region_var(self.origin.clone()) | ||
} | ||
_ => { | ||
r | ||
} | ||
} | ||
} | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,46 @@ | ||
// Copyright 2016 The Rust Project Developers. See the COPYRIGHT | ||
// file at the top-level directory of this distribution and at | ||
// http://rust-lang.org/COPYRIGHT. | ||
// | ||
// Licensed under the Apache License, Version 2.0 <LICENSE-APACHE or | ||
// http://www.apache.org/licenses/LICENSE-2.0> or the MIT license | ||
// <LICENSE-MIT or http://opensource.org/licenses/MIT>, at your | ||
// option. This file may not be copied, modified, or distributed | ||
// except according to those terms. | ||
|
||
// Regression test for #37655. The problem was a false edge created by | ||
// coercion that wound up requiring that `'a` (in `split()`) outlive | ||
// `'b`, which shouldn't be necessary. | ||
|
||
#![allow(warnings)] | ||
|
||
trait SliceExt<T> { | ||
type Item; | ||
|
||
fn get_me<I>(&self, index: I) -> &I::Output | ||
where I: SliceIndex<Self::Item>; | ||
} | ||
|
||
impl<T> SliceExt<T> for [T] { | ||
type Item = T; | ||
|
||
fn get_me<I>(&self, index: I) -> &I::Output | ||
where I: SliceIndex<T> | ||
{ | ||
panic!() | ||
} | ||
} | ||
|
||
pub trait SliceIndex<T> { | ||
type Output: ?Sized; | ||
} | ||
|
||
impl<T> SliceIndex<T> for usize { | ||
type Output = T; | ||
} | ||
|
||
fn foo<'a, 'b>(split: &'b [&'a [u8]]) -> &'a [u8] { | ||
split.get_me(0) | ||
} | ||
|
||
fn main() { } |
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will break down once lazy normalization happens, right? Not that it blocks the PR.