Repository navigation
Compiler gets lifetime scope wrong #28970
Description
Please check the code bellow
https://play.rust-lang.org/?gist=c0dd3d93bde346c4bd4d&version=nightly
#![feature(drain)]
use std::sync::{Arc, RwLock};
fn main() {
let files = RwLock::new(vec![Arc::new(1u32)]);
// WONT compile
let a: Vec<_> = files.write().unwrap().drain(..1).collect();
// WONT compile
let a: Vec<_> = {
let mut temp = files.write().unwrap();
temp.drain(..1).collect()
};
// compiles
let a: Vec<_> = {
let mut temp = files.write().unwrap();
let res = temp.drain(..1).collect();
res
};
println!("{:?}", a);
}
I suppose all of them should compile as they do the same thing, but only the last one does.
Activity
[-]Compiler gets lifetime scope wrong in an oneliner[/-][+]Compiler gets lifetime scope wrong[/+]steveklabnik commentedon Nov 11, 2015
@gankro is this the expected behavior of drian?
Gankra commentedon Nov 12, 2015
Nothin' to do with Drain in particular. Just the compiler being suboptimal with temporary lifetimes.
steveklabnik commentedon Apr 30, 2017
Triage: no change, still reproduces
memoryruins commentedon Jan 30, 2019
Triage: now compiles on 2018.
2015 errors:
rustc: 1.32.0pnkfelix commentedon Feb 27, 2019
Reopening: Our current policy is if the 2015 edition alone suffers from a bug that is scheduled to be fixed by NLL (i.e. tagged NLL-fixed-by-NLL) then we leave such issues open until NLL is turned on in the 2015 edition.
Auto merge of #59114 - matthewjasper:enable-migate-2015, r=<try>
Auto merge of #59114 - matthewjasper:enable-migate-2015, r=pnkfelix
Auto merge of #59114 - matthewjasper:enable-migate-2015, r=pnkfelix