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

fn main() {
    let x: Box<isize> = Box::new(0);

    println!("{}", x + 1);
    //~^ ERROR cannot add `{integer}` to `Box<isize>`
}
Change prints: @T -> Gc<T> , ~T -> Box<T> Fixes #14915 2014-06-15 17:04:55 +00:00			`fn main() {`
Remove even more box syntax uses from src/test Prior work, notably 6550021124451628b1efc60c59284465b109e3aa from #88316 has removed box syntax from most of the testsuite. However, some tests were left out. This commit removes box_syntax uses from more locations in src/test. Some tests that are very box syntax specific are not being migrated. 2022-07-07 02:36:10 +00:00			`let x: Box<isize> = Box::new(0);`
Change prints: @T -> Gc<T> , ~T -> Box<T> Fixes #14915 2014-06-15 17:04:55 +00:00
Merge ty::TyBox into ty::TyAdt 2017-01-21 14:40:31 +00:00			`println!("{}", x + 1);`
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 07:40:56 +00:00			//~^ ERROR cannot add `{integer}` to `Box<isize>`
Change prints: @T -> Gc<T> , ~T -> Box<T> Fixes #14915 2014-06-15 17:04:55 +00:00			`}`