rust/src/test/run-pass/issue-25549-multiple-drop.rs
Björn Steinbrink b802b18730 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 14:25:35 +02:00

42 lines
1.1 KiB
Rust

// Copyright 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.
struct Foo<'r>(&'r mut i32);
impl<'r> Drop for Foo<'r> {
fn drop(&mut self) {
*self.0 += 1;
}
}
trait Trait {}
impl<'r> Trait for Foo<'r> {}
struct Holder<T: ?Sized>(T);
fn main() {
let mut drops = 0;
{
let y = &Holder([Foo(&mut drops)]) as &Holder<[Foo]>;
// this used to cause an extra drop of the Foo instance
let x = &y.0;
}
assert_eq!(1, drops);
drops = 0;
{
let y = &Holder(Foo(&mut drops)) as &Holder<Trait>;
// this used to cause an extra drop of the Foo instance
let x = &y.0;
}
assert_eq!(1, drops);
}