rust/tests/ui/deriving/deriving-in-fn.rs

// run-pass

#![allow(dead_code)]

pub fn main() {
    #[derive(Debug)]
    struct Foo {
        foo: isize,
    }

    let f = Foo { foo: 10 };
    format!("{:?}", f);
}
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 07:18:55 -05:00			`// run-pass`
Ignore automatically derived impls of `Clone` and `Debug` in dead code analysis 2021-05-21 12:35:49 -05:00
			`#![allow(dead_code)]`

Expand ItemDecorator extensions in all contexts Now that fold_item can return multiple items, this is pretty trivial. It also recursively expands generated items so ItemDecorators can generate items that are tagged with ItemDecorators! Closes #4913 2014-02-14 00:57:43 -06:00			`pub fn main() {`
s/Show/Debug/g 2015-01-28 07:34:18 -06:00			`#[derive(Debug)]`
Expand ItemDecorator extensions in all contexts Now that fold_item can return multiple items, this is pretty trivial. It also recursively expands generated items so ItemDecorators can generate items that are tagged with ItemDecorators! Closes #4913 2014-02-14 00:57:43 -06:00			`struct Foo {`
Mass rename uint/int to usize/isize Now that support has been removed, all lingering use cases are renamed. 2015-03-25 19:06:52 -05:00			`foo: isize,`
Expand ItemDecorator extensions in all contexts Now that fold_item can return multiple items, this is pretty trivial. It also recursively expands generated items so ItemDecorators can generate items that are tagged with ItemDecorators! Closes #4913 2014-02-14 00:57:43 -06:00			`}`

			`let f = Foo { foo: 10 };`
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 02:09:35 -06:00			`format!("{:?}", f);`
Expand ItemDecorator extensions in all contexts Now that fold_item can return multiple items, this is pretty trivial. It also recursively expands generated items so ItemDecorators can generate items that are tagged with ItemDecorators! Closes #4913 2014-02-14 00:57:43 -06:00			`}`