rust/src/test/run-pass/issues/issue-14399.rs

// run-pass
// #14399
// We'd previously ICE if we had a method call whose return
// value was coerced to a trait object. (v.clone() returns Box<B1>
// which is coerced to Box<A>).

// pretty-expanded FIXME #23616

#![feature(box_syntax)]

#[derive(Clone)]
struct B1;

trait A { fn foo(&self) {} }
impl A for B1 {}

fn main() {
    let v: Box<_> = box B1;
    let _c: Box<A> = v.clone();
}
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`
librustc: Don't overwrite vtables when coercing to trait object. 2014-06-11 22:01:48 +00:00			`// #14399`
			`// We'd previously ICE if we had a method call whose return`
			`// value was coerced to a trait object. (v.clone() returns Box<B1>`
			`// which is coerced to Box<A>).`

rustdoc: Replace no-pretty-expanded with pretty-expanded Now that features must be declared expanded source often does not compile. This adds 'pretty-expanded' to a bunch of test cases that still work. 2015-03-22 20:13:15 +00:00			`// pretty-expanded FIXME #23616`

fallout: run-pass tests that use box. (many could be ported to `Box::new` instead in the future.) 2015-01-08 01:25:56 +00:00			`#![feature(box_syntax)]`

Use `derive` rather than `deriving` in tests 2014-12-31 04:32:49 +00:00			`#[derive(Clone)]`
librustc: Don't overwrite vtables when coercing to trait object. 2014-06-11 22:01:48 +00:00			`struct B1;`

Round 3 test fixes and conflicts 2015-02-18 23:58:07 +00:00			`trait A { fn foo(&self) {} }`
librustc: Don't overwrite vtables when coercing to trait object. 2014-06-11 22:01:48 +00:00			`impl A for B1 {}`

			`fn main() {`
Add `: Box<_>` or `::Box<_>` type annotations to various places. This is the kind of change that one is expected to need to make to accommodate overloaded-`box`. ---- Note that this is not all of the changes necessary to accommodate Issue 22181. It is merely the subset of those cases where there was already a let-binding in place that made it easy to add the necesasry type ascription. (For unnamed intermediate `Box` values, one must go down a different route; `Box::new` is the option that maximizes portability, but has potential inefficiency depending on whether the call is inlined.) ---- There is one place worth note, `run-pass/coerce-match.rs`, where I used an ugly form of `Box<_>` type ascription where I would have preferred to use `Box::new` to accommodate overloaded-`box`. I deliberately did not use `Box::new` here, because that is already done in coerce-match-calls.rs. ---- Precursor for overloaded-`box` and placement-`in`; see Issue 22181. 2015-02-17 20:41:32 +00:00			`let v: Box<_> = box B1;`
librustc: Don't overwrite vtables when coercing to trait object. 2014-06-11 22:01:48 +00:00			`let _c: Box<A> = v.clone();`
			`}`