rust/tests/ui/nll/issue-52059-report-when-borrow-and-drop-conflict.rs

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

31 lines
863 B
Rust
Raw Normal View History

// rust-lang/rust#52059: Regardless of whether you are moving out of a
2018-10-22 11:21:55 -05:00
// Drop type or just introducing an inadvertent alias via a borrow of
// one of its fields, it is useful to be reminded of the significance
// of the fact that the type implements Drop.
pub struct S<'a> { url: &'a mut String }
impl<'a> Drop for S<'a> { fn drop(&mut self) { } }
fn finish_1(s: S) -> &mut String {
s.url
}
//~^^ ERROR borrow may still be in use when destructor runs
fn finish_2(s: S) -> &mut String {
let p = &mut *s.url; p
}
//~^^ ERROR borrow may still be in use when destructor runs
fn finish_3(s: S) -> &mut String {
let p: &mut _ = s.url; p
}
//~^^ ERROR borrow may still be in use when destructor runs
fn finish_4(s: S) -> &mut String {
let p = s.url; p
}
//~^^ ERROR cannot move out of type `S<'_>`, which implements the `Drop` trait
fn main() {}