Skip to content

Commit ebe1d8e

Browse files
committed
Add run-pass case for issue #14308
Enum wildcard patterns in match behave wrong when applied to tuple structs. They either ICE or cause an LLVM error.
1 parent e546452 commit ebe1d8e

File tree

1 file changed

+32
-0
lines changed

1 file changed

+32
-0
lines changed

src/test/run-pass/issue-14308.rs

Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
// Copyright 2014 The Rust Project Developers. See the COPYRIGHT
2+
// file at the top-level directory of this distribution and at
3+
// http://rust-lang.org/COPYRIGHT.
4+
//
5+
// Licensed under the Apache License, Version 2.0 <LICENSE-APACHE or
6+
// http://www.apache.org/licenses/LICENSE-2.0> or the MIT license
7+
// <LICENSE-MIT or http://opensource.org/licenses/MIT>, at your
8+
// option. This file may not be copied, modified, or distributed
9+
// except according to those terms.
10+
11+
struct A(int);
12+
struct B;
13+
14+
fn main() {
15+
let x = match A(3) {
16+
A(..) => 1
17+
};
18+
assert_eq!(x, 1);
19+
let x = match A(4) {
20+
A(1) => 1,
21+
A(..) => 2
22+
};
23+
assert_eq!(x, 2);
24+
25+
// This next test uses a (..) wildcard match on a nullary struct.
26+
// There's no particularly good reason to support this, but it's currently allowed,
27+
// and this makes sure it doesn't ICE or break LLVM.
28+
let x = match B {
29+
B(..) => 3
30+
};
31+
assert_eq!(x, 3);
32+
}

0 commit comments

Comments
 (0)