rust/tests/ui/or-patterns/or-patterns-syntactic-fail.stderr

error: top-level or-patterns are not allowed in function parameters
  --> $DIR/or-patterns-syntactic-fail.rs:15:13
   |
LL |     fn fun1(A | B: E) {}
   |             ^^^^^ help: wrap the pattern in parentheses: `(A | B)`

error: top-level or-patterns are not allowed in function parameters
  --> $DIR/or-patterns-syntactic-fail.rs:18:13
   |
LL |     fn fun2(| A | B: E) {}
   |             ^^^^^^^ help: wrap the pattern in parentheses: `(A | B)`

error: top-level or-patterns are not allowed in `let` bindings
  --> $DIR/or-patterns-syntactic-fail.rs:23:9
   |
LL |     let A | B: E = A;
   |         ^^^^^ help: wrap the pattern in parentheses: `(A | B)`

error: top-level or-patterns are not allowed in `let` bindings
  --> $DIR/or-patterns-syntactic-fail.rs:26:9
   |
LL |     let | A | B: E = A;
   |         ^^^^^^^ help: wrap the pattern in parentheses: `(A | B)`

error[E0369]: no implementation for `E | ()`
  --> $DIR/or-patterns-syntactic-fail.rs:11:22
   |
LL |     let _ = |A | B: E| ();
   |                  ----^ -- ()
   |                  |
   |                  E
   |
note: an implementation of `BitOr<()>` might be missing for `E`
  --> $DIR/or-patterns-syntactic-fail.rs:6:1
   |
LL | enum E { A, B }
   | ^^^^^^ must implement `BitOr<()>`
note: the trait `BitOr` must be implemented
  --> $SRC_DIR/core/src/ops/bit.rs:LL:COL

error: aborting due to 5 previous errors

For more information about this error, try `rustc --explain E0369`.
use pat<no_top_alt> for patterns in let bindings 2021-02-12 18:04:37 -06:00			`error: top-level or-patterns are not allowed in function parameters`
update tests 2020-11-21 16:05:17 -06:00			`--> $DIR/or-patterns-syntactic-fail.rs:15:13`
or-patterns: add syntactic tests. 2019-08-18 16:53:08 -05:00			`\|`
parser: gracefully handle `fn foo(A \| B: type)`. 2019-08-24 21:39:28 -05:00			`LL \| fn fun1(A \| B: E) {}`
Simplify pattern grammar by allowing nested leading vert Along the way, we also implement a handful of diagnostics improvements and fixes, particularly with respect to the special handling of `\|\|` in place of `\|` and when there are leading verts in function params, which don't allow top-level or-patterns anyway. 2021-02-07 20:40:33 -06:00			\| ^^^^^ help: wrap the pattern in parentheses: `(A \| B)`
parser: gracefully handle `fn foo(A \| B: type)`. 2019-08-24 21:39:28 -05:00
use pat<no_top_alt> for patterns in let bindings 2021-02-12 18:04:37 -06:00			`error: top-level or-patterns are not allowed in function parameters`
update tests 2020-11-21 16:05:17 -06:00			`--> $DIR/or-patterns-syntactic-fail.rs:18:13`
parser: gracefully handle `fn foo(A \| B: type)`. 2019-08-24 21:39:28 -05:00			`\|`
			`LL \| fn fun2(\| A \| B: E) {}`
Simplify pattern grammar by allowing nested leading vert Along the way, we also implement a handful of diagnostics improvements and fixes, particularly with respect to the special handling of `\|\|` in place of `\|` and when there are leading verts in function params, which don't allow top-level or-patterns anyway. 2021-02-07 20:40:33 -06:00			\| ^^^^^^^ help: wrap the pattern in parentheses: `(A \| B)`
or-patterns: add syntactic tests. 2019-08-18 16:53:08 -05:00
use pat<no_top_alt> for patterns in let bindings 2021-02-12 18:04:37 -06:00			error: top-level or-patterns are not allowed in `let` bindings
update tests 2020-11-21 16:05:17 -06:00			`--> $DIR/or-patterns-syntactic-fail.rs:23:9`
use pat<no_top_alt> for patterns in let bindings 2021-02-12 18:04:37 -06:00			`\|`
			`LL \| let A \| B: E = A;`
			\| ^^^^^ help: wrap the pattern in parentheses: `(A \| B)`

			error: top-level or-patterns are not allowed in `let` bindings
update tests 2020-11-21 16:05:17 -06:00			`--> $DIR/or-patterns-syntactic-fail.rs:26:9`
use pat<no_top_alt> for patterns in let bindings 2021-02-12 18:04:37 -06:00			`\|`
			`LL \| let \| A \| B: E = A;`
			\| ^^^^^^^ help: wrap the pattern in parentheses: `(A \| B)`

Update UI test expectations 2019-12-10 15:03:13 -06:00			error[E0369]: no implementation for `E \| ()`
update tests 2020-11-21 16:05:17 -06:00			`--> $DIR/or-patterns-syntactic-fail.rs:11:22`
or-patterns: add syntactic tests. 2019-08-18 16:53:08 -05:00			`\|`
			`LL \| let _ = \|A \| B: E\| ();`
			`\| ----^ -- ()`
			`\| \|`
			`\| E`
			`\|`
Provide RHS type hint when reporting operator error 2023-04-26 19:57:13 -05:00			note: an implementation of `BitOr<()>` might be missing for `E`
Consider unfulfilled obligations in binop errors When encountering a binop where the types would have been accepted, if all the predicates had been fulfilled, include information about the predicates and suggest appropriate `#[derive]`s if possible. Point at trait(s) that needs to be `impl`emented. 2021-09-28 09:48:54 -05:00			`--> $DIR/or-patterns-syntactic-fail.rs:6:1`
			`\|`
			`LL \| enum E { A, B }`
Provide RHS type hint when reporting operator error 2023-04-26 19:57:13 -05:00			\| ^^^^^^ must implement `BitOr<()>`
Inform the user which trait is meant in the diagnostic itself instead of relying on the span making it obvious 2022-12-12 05:55:46 -06:00			note: the trait `BitOr` must be implemented
Consider unfulfilled obligations in binop errors When encountering a binop where the types would have been accepted, if all the predicates had been fulfilled, include information about the predicates and suggest appropriate `#[derive]`s if possible. Point at trait(s) that needs to be `impl`emented. 2021-09-28 09:48:54 -05:00			`--> $SRC_DIR/core/src/ops/bit.rs:LL:COL`
or-patterns: add syntactic tests. 2019-08-18 16:53:08 -05:00
use pat<no_top_alt> for patterns in let bindings 2021-02-12 18:04:37 -06:00			`error: aborting due to 5 previous errors`
or-patterns: add syntactic tests. 2019-08-18 16:53:08 -05:00
Simplify pattern grammar by allowing nested leading vert Along the way, we also implement a handful of diagnostics improvements and fixes, particularly with respect to the special handling of `\|\|` in place of `\|` and when there are leading verts in function params, which don't allow top-level or-patterns anyway. 2021-02-07 20:40:33 -06:00			For more information about this error, try `rustc --explain E0369`.