rust/tests/ui/lifetimes/array-pattern-matching-10396.rs

//! Regression test for https://github.com/rust-lang/rust/issues/10396

//@ check-pass
#![allow(dead_code)]
#[derive(Debug)]
enum Foo<'s> {
    V(&'s str)
}

fn f(arr: &[&Foo]) {
    for &f in arr {
        println!("{:?}", f);
    }
}

fn main() {}
comments 2025-07-18 22:06:07 +05:00			`//! Regression test for https://github.com/rust-lang/rust/issues/10396`

Use check-pass in ui tests where appropriate 2019-11-04 00:00:00 +00:00			`//@ check-pass`
Add `#![allow(..)]` as necessary to get re-migrated run-pass tests compiling with clean stderr again. Most were added mechanically. 2018-09-25 23:51:35 +02:00			`#![allow(dead_code)]`
s/Show/Debug/g 2015-01-28 08:34:18 -05:00			`#[derive(Debug)]`
Add tests for E-needstest issues 2014-11-03 00:58:00 +01:00			`enum Foo<'s> {`
			`V(&'s str)`
			`}`

			`fn f(arr: &[&Foo]) {`
`for x in xs.iter()` -> `for x in &xs` 2015-01-31 12:20:46 -05:00			`for &f in arr {`
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!("{:?}", f);`
Add tests for E-needstest issues 2014-11-03 00:58:00 +01:00			`}`
			`}`

			`fn main() {}`