rust/tests/ui/pattern/pattern-tyvar.rs

enum Bar { T1((), Option<Vec<isize>>), T2 }

fn foo(t: Bar) {
    match t {
      Bar::T1(_, Some::<isize>(x)) => { //~ ERROR mismatched types
        println!("{}", x);
      }
      _ => { panic!(); }
    }
}

fn main() { }
make non_camel_case_types an early lint 2018-12-16 22:21:47 -05:00			`enum Bar { T1((), Option<Vec<isize>>), T2 }`
Two tests that the typechecker correctly unifies type arguments in patterns with their expected tag types 2011-05-14 19:03:08 -07:00
make non_camel_case_types an early lint 2018-12-16 22:21:47 -05:00			`fn foo(t: Bar) {`
Convert alt to match. Stop parsing alt 2012-08-06 12:34:08 -07:00			`match t {`
make non_camel_case_types an early lint 2018-12-16 22:21:47 -05:00			`Bar::T1(_, Some::<isize>(x)) => { //~ ERROR mismatched types`
Remove libdebug and update tests. 2014-10-14 21:07:11 -04:00			`println!("{}", x);`
Register snapshots and switch logging over to use of log_full or #error / #debug. 2011-12-22 14:42:52 -08:00			`}`
Rename fail! to panic! https://github.com/rust-lang/rfcs/pull/221 The current terminology of "task failure" often causes problems when writing or speaking about code. You often want to talk about the possibility of an operation that returns a Result "failing", but cannot because of the ambiguity with task failure. Instead, you have to speak of "the failing case" or "when the operation does not succeed" or other circumlocutions. Likewise, we use a "Failure" header in rustdoc to describe when operations may fail the task, but it would often be helpful to separate out a section describing the "Err-producing" case. We have been steadily moving away from task failure and toward Result as an error-handling mechanism, so we should optimize our terminology accordingly: Result-producing functions should be easy to describe. To update your code, rename any call to `fail!` to `panic!` instead. Assuming you have not created your own macro named `panic!`, this will work on UNIX based systems: grep -lZR 'fail!' . \| xargs -0 -l sed -i -e 's/fail!/panic!/g' You can of course also do this by hand. [breaking-change] 2014-10-09 15:17:22 -04:00			`_ => { panic!(); }`
Register snapshots and switch logging over to use of log_full or #error / #debug. 2011-12-22 14:42:52 -08:00			`}`
			`}`
Two tests that the typechecker correctly unifies type arguments in patterns with their expected tag types 2011-05-14 19:03:08 -07:00
Port the tests to the typaram foo<T> syntax. 2011-08-10 09:27:22 -07:00			`fn main() { }`