os-rust/tests/ui/deriving/issue-19358.rs

//@ run-pass

#![allow(dead_code)]

trait Trait { fn dummy(&self) { } }

#[derive(Debug)]
struct Foo<T: Trait> {
    foo: T,
}

#[derive(Debug)]
struct Bar<T> where T: Trait {
    bar: T,
}

impl Trait for isize {}

fn main() {
    let a = Foo { foo: 12 };
    let b = Bar { bar: 12 };
    println!("{:?} {:?}", a, b);
}
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 14:18:55 +02:00			`//@ run-pass`
Ignore automatically derived impls of `Clone` and `Debug` in dead code analysis 2021-05-21 19:35:49 +02:00
			`#![allow(dead_code)]`

Fallout: tests. As tests frequently elide things, lots of changes here. Some of this may have been poorly rebased, though I tried to be careful and preserve the spirit of the test. 2015-02-12 10:29:52 -05:00			`trait Trait { fn dummy(&self) { } }`
libsyntax: Make deriving also respect where bounds. 2014-12-14 00:35:35 -05:00
s/Show/Debug/g 2015-01-28 08:34:18 -05:00			`#[derive(Debug)]`
libsyntax: Make deriving also respect where bounds. 2014-12-14 00:35:35 -05:00			`struct Foo<T: Trait> {`
			`foo: T,`
			`}`

s/Show/Debug/g 2015-01-28 08:34:18 -05:00			`#[derive(Debug)]`
libsyntax: Make deriving also respect where bounds. 2014-12-14 00:35:35 -05:00			`struct Bar<T> where T: Trait {`
			`bar: T,`
			`}`

Mass rename uint/int to usize/isize Now that support has been removed, all lingering use cases are renamed. 2015-03-25 17:06:52 -07:00			`impl Trait for isize {}`
libsyntax: Make deriving also respect where bounds. 2014-12-14 00:35:35 -05:00
			`fn main() {`
Remove all `i` suffixes 2015-01-25 22:05:03 +01:00			`let a = Foo { foo: 12 };`
			`let b = Bar { bar: 12 };`
core: split into fmt::Show and fmt::String fmt::Show is for debugging, and can and should be implemented for all public types. This trait is used with `{:?}` syntax. There still exists #[derive(Show)]. fmt::String is for types that faithfully be represented as a String. Because of this, there is no way to derive fmt::String, all implementations must be purposeful. It is used by the default format syntax, `{}`. This will break most instances of `{}`, since that now requires the type to impl fmt::String. In most cases, replacing `{}` with `{:?}` is the correct fix. Types that were being printed specifically for users should receive a fmt::String implementation to fix this. Part of #20013 [breaking-change] 2014-12-20 00:09:35 -08:00			`println!("{:?} {:?}", a, b);`
libsyntax: Make deriving also respect where bounds. 2014-12-14 00:35:35 -05:00			`}`