rust/tests/ui/enum/match-either-enum-variants-6117.rs

// https://github.com/rust-lang/rust/issues/6117
//@ run-pass
#![allow(dead_code)]

enum Either<T, U> { Left(T), Right(U) }

pub fn main() {
    match Either::Left(Box::new(17)) {
        Either::Right(()) => {}
        _ => {}
    }
}
Add test batch 1 2025-08-20 14:02:39 -04:00			`// https://github.com/rust-lang/rust/issues/6117`
[AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives 2024-02-16 20:02:50 +00:00			`//@ run-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)]`
rustdoc: Replace no-pretty-expanded with pretty-expanded Now that features must be declared expanded source often does not compile. This adds 'pretty-expanded' to a bunch of test cases that still work. 2015-03-22 13:13:15 -07:00
Remove std::either 2013-12-25 21:55:05 -08:00			`enum Either<T, U> { Left(T), Right(U) }`

The null case of a nullable-poiner enum might not be nullary. Cases like `Either<@int,()>` have a null case with at most one value but a nonzero number of fields; if we misreport this, then bad things can happen inside of, for example, pattern matching. Closes #6117. 2013-04-30 11:36:22 -07:00			`pub fn main() {`
Switched to Box::new in many places. Many of the modifications putting in `Box::new` calls also include a pointer to Issue 22405, which tracks going back to `box <expr>` if possible in the future. (Still tried to use `Box<_>` where it sufficed; thus some tests still have `box_syntax` enabled, as they use a mix of `box` and `Box::new`.) Precursor for overloaded-`box` and placement-`in`; see Issue 22181. 2015-02-15 09:52:21 +01:00			`match Either::Left(Box::new(17)) {`
Switch to purely namespaced enums This breaks code that referred to variant names in the same namespace as their enum. Reexport the variants in the old location or alter code to refer to the new locations: ``` pub enum Foo { A, B } fn main() { let a = A; } ``` => ``` pub use self::Foo::{A, B}; pub enum Foo { A, B } fn main() { let a = A; } ``` or ``` pub enum Foo { A, B } fn main() { let a = Foo::A; } ``` [breaking-change] 2014-11-06 00:05:53 -08:00			`Either::Right(()) => {}`
The null case of a nullable-poiner enum might not be nullary. Cases like `Either<@int,()>` have a null case with at most one value but a nonzero number of fields; if we misreport this, then bad things can happen inside of, for example, pattern matching. Closes #6117. 2013-04-30 11:36:22 -07:00			`_ => {}`
			`}`
			`}`