rust/tests/ui/traits/issue-32963.rs

use std::mem;

trait Misc {}

fn size_of_copy<T: Copy+?Sized>() -> usize { mem::size_of::<T>() }

fn main() {
    size_of_copy::<dyn Misc + Copy>();
    //~^ ERROR only auto traits can be used as additional traits in a trait object
    //~| ERROR the trait bound `dyn Misc: Copy` is not satisfied
}
require the existential bounds of an object type to be object-safe This is required, as Copy and Sized are object-unsafe. As a soundness fix, this is a [breaking-change] Fixes #32963 2016-04-22 02:31:04 +03:00			`use std::mem;`

			`trait Misc {}`

			`fn size_of_copy<T: Copy+?Sized>() -> usize { mem::size_of::<T>() }`

			`fn main() {`
Update ui test suite to use dyn 2019-05-28 14:46:13 -04:00			`size_of_copy::<dyn Misc + Copy>();`
Fix checking of auto trait bounds in trait objects. Any auto trait is allowed in trait object bounds. Fix duplicate check of type and lifetime parameter count. 2017-11-04 19:44:19 -02:00			`//~^ ERROR only auto traits can be used as additional traits in a trait object`
pretty: trim paths of unique symbols If a symbol name can only be imported from one place for a type, and as long as it was not glob-imported anywhere in the current crate, we can trim its printed path and print only the name. This has wide implications on error messages with types, for example, shortening `std::vec::Vec` to just `Vec`, as long as there is no other `Vec` importable anywhere. This adds a new '-Z trim-diagnostic-paths=false' option to control this feature. On the good path, with no diagnosis printed, we should try to avoid issuing this query, so we need to prevent trimmed_def_paths query on several cases. This change also relies on a previous commit that differentiates between `Debug` and `Display` on various rustc types, where the latter is trimmed and presented to the user and the former is not. 2020-09-02 10:40:56 +03:00			//~\| ERROR the trait bound `dyn Misc: Copy` is not satisfied
require the existential bounds of an object type to be object-safe This is required, as Copy and Sized are object-unsafe. As a soundness fix, this is a [breaking-change] Fixes #32963 2016-04-22 02:31:04 +03:00			`}`