rust/tests/ui/structs-enums/tuple-struct-construct.rs

//@ run-pass
#[allow(dead_code)]
#[derive(Debug)]
struct Foo(isize, isize);

pub fn main() {
    let x = Foo(1, 2);
    println!("{:?}", x);
}
[AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives 2024-02-16 20:02:50 +00:00			`//@ run-pass`
Adjust compiler tests for unused_tuple_struct_fields -> dead_code 2023-12-27 17:11:58 -05:00			`#[allow(dead_code)]`
s/Show/Debug/g 2015-01-28 08:34:18 -05:00			`#[derive(Debug)]`
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			`struct Foo(isize, isize);`
rustc: Translate tuple struct constructors 2012-10-24 14:36:00 -07:00
check-fast fallout from removing export, r=burningtree 2013-02-01 19:43:17 -08:00			`pub fn main() {`
rustc: Translate tuple struct constructors 2012-10-24 14:36:00 -07:00			`let x = Foo(1, 2);`
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!("{:?}", x);`
rustc: Translate tuple struct constructors 2012-10-24 14:36:00 -07:00			`}`