rust/tests/ui/issues/issue-25515.rs

// run-pass
use std::rc::Rc;

struct Foo<'r>(&'r mut i32);

impl<'r> Drop for Foo<'r> {
    fn drop(&mut self) {
        *self.0 += 1;
    }
}

fn main() {
    let mut drops = 0;

    {
        let _: Rc<dyn Send> = Rc::new(Foo(&mut drops));
    }

    assert_eq!(1, drops);
}
Add `// run-pass` annotations to all the tests under `ui/run-pass/`. (I may have accidentally added it to some auxilliary crates as well; my emacs-macro-based methodology was pretty crude.) 2018-08-30 12:18:55 +00:00			`// run-pass`
Don't call drop when taking the address of unsized fields When taking the address of an unsized field we generate a rvalue datum for the field and then convert it to an lvalue datum. At that point, cleanup is scheduled for the field, leading to multiple drop calls. The problem is that we generate an rvalue datum for the field, since the pointer does not own the data and there's already cleanup scheduled elsewhere by the true owner. Instead, an lvalue datum must be created. Thanks to @eddyb for identifying the underlying cause and suggesting the correct fix. Fixes #25549 Fixes #25515 2015-05-19 07:50:48 +00:00			`use std::rc::Rc;`

			`struct Foo<'r>(&'r mut i32);`

			`impl<'r> Drop for Foo<'r> {`
			`fn drop(&mut self) {`
			`*self.0 += 1;`
			`}`
			`}`

			`fn main() {`
			`let mut drops = 0;`

			`{`
Update run-pass test suite to use dyn 2019-05-28 18:47:21 +00:00			`let _: Rc<dyn Send> = Rc::new(Foo(&mut drops));`
Don't call drop when taking the address of unsized fields When taking the address of an unsized field we generate a rvalue datum for the field and then convert it to an lvalue datum. At that point, cleanup is scheduled for the field, leading to multiple drop calls. The problem is that we generate an rvalue datum for the field, since the pointer does not own the data and there's already cleanup scheduled elsewhere by the true owner. Instead, an lvalue datum must be created. Thanks to @eddyb for identifying the underlying cause and suggesting the correct fix. Fixes #25549 Fixes #25515 2015-05-19 07:50:48 +00:00			`}`

			`assert_eq!(1, drops);`
			`}`