diff options
| author | LeSeulArtichaut <leseulartichaut@gmail.com> | 2019-12-11 23:11:32 +0100 |
|---|---|---|
| committer | LeSeulArtichaut <leseulartichaut@gmail.com> | 2019-12-12 20:56:14 +0100 |
| commit | eac6fac10b572d4912d0bcd455c12909f63914b7 (patch) | |
| tree | 5a3620cace948a87da14c57a3631a09b7dd77e1a /src/test/ui/or-patterns | |
| parent | 27810e246c89777f39441d6cc050e540cb2e54e0 (diff) | |
Update tests
Diffstat (limited to 'src/test/ui/or-patterns')
| -rw-r--r-- | src/test/ui/or-patterns/or-patterns-syntactic-fail.rs | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/test/ui/or-patterns/or-patterns-syntactic-fail.rs b/src/test/ui/or-patterns/or-patterns-syntactic-fail.rs index b676ea851a3..ce6836f30f9 100644 --- a/src/test/ui/or-patterns/or-patterns-syntactic-fail.rs +++ b/src/test/ui/or-patterns/or-patterns-syntactic-fail.rs @@ -21,7 +21,7 @@ use E::*; fn no_top_level_or_patterns() { // We do *not* allow or-patterns at the top level of lambdas... - let _ = |A | B: E| (); //~ ERROR binary operation `|` cannot be applied to type `E` + let _ = |A | B: E| (); //~ ERROR no implementation for `E | ()` // -------- This looks like an or-pattern but is in fact `|A| (B: E | ())`. // ...and for now neither do we allow or-patterns at the top level of functions. |