rust/tests/ui/error-codes/E0004-2.stderr

error[E0004]: non-exhaustive patterns: `None` and `Some(_)` not covered
  --> $DIR/E0004-2.rs:4:11
   |
LL |     match x { }
   |           ^ patterns `None` and `Some(_)` not covered
   |
note: `Option<i32>` defined here
  --> $SRC_DIR/core/src/option.rs:LL:COL
  ::: $SRC_DIR/core/src/option.rs:LL:COL
   |
   = note: not covered
  ::: $SRC_DIR/core/src/option.rs:LL:COL
   |
   = note: not covered
   = note: the matched value is of type `Option<i32>`
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern, a match arm with multiple or-patterns as shown, or multiple match arms
   |
LL ~     match x {
LL +         None | Some(_) => todo!(),
LL ~     }
   |

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0004`.
Forgot to update some test outputs 2019-12-04 16:39:33 +00:00			error[E0004]: non-exhaustive patterns: `None` and `Some(_)` not covered
tests: remove ignore directives from tests that mention core/alloc/std spans. 2020-04-01 01:10:13 +00:00			`--> $DIR/E0004-2.rs:4:11`
Move some E0XXX to `ui` 2018-02-08 03:35:35 +00:00			`\|`
Update tests 2019-03-09 12:03:44 +00:00			`LL \| match x { }`
Forgot to update some test outputs 2019-12-04 16:39:33 +00:00			\| ^ patterns `None` and `Some(_)` not covered
Remove trailing whitespace from error messages 2021-06-10 11:52:00 +00:00			`\|`
Point at uncovered variants in enum definition in `note` instead of a `span_label` This makes the order of the output always consistent: 1. Place of the `match` missing arms 2. The `enum` definition span 3. The structured suggestion to add a fallthrough arm 2021-12-16 05:06:44 +00:00			note: `Option<i32>` defined here
			`--> $SRC_DIR/core/src/option.rs:LL:COL`
Avoid rendering empty annotations 2022-12-12 15:25:04 +00:00			`::: $SRC_DIR/core/src/option.rs:LL:COL`
			`\|`
			`= note: not covered`
			`::: $SRC_DIR/core/src/option.rs:LL:COL`
			`\|`
			`= note: not covered`
pretty: trim paths of unique symbols If a symbol name can only be imported from one place for a type, and as long as it was not glob-imported anywhere in the current crate, we can trim its printed path and print only the name. This has wide implications on error messages with types, for example, shortening `std::vec::Vec` to just `Vec`, as long as there is no other `Vec` importable anywhere. This adds a new '-Z trim-diagnostic-paths=false' option to control this feature. On the good path, with no diagnosis printed, we should try to avoid issuing this query, so we need to prevent trimmed_def_paths query on several cases. This change also relies on a previous commit that differentiates between `Debug` and `Display` on various rustc types, where the latter is trimmed and presented to the user and the former is not. 2020-09-02 07:40:56 +00:00			= note: the matched value is of type `Option<i32>`
Change wording of suggestion to add missing `match` arm 2021-12-16 22:46:13 +00:00			`help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern, a match arm with multiple or-patterns as shown, or multiple match arms`
When encountering a match expr with no arms, suggest it Given ```rust match Some(42) {} ``` suggest ```rust match Some(42) { None \| Some(_) => todo!(), } ``` 2021-12-16 02:05:58 +00:00			`\|`
			`LL ~ match x {`
			`LL + None \| Some(_) => todo!(),`
			`LL ~ }`
			`\|`
Move some E0XXX to `ui` 2018-02-08 03:35:35 +00:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 15:44:16 +00:00			`error: aborting due to 1 previous error`
Move some E0XXX to `ui` 2018-02-08 03:35:35 +00:00
update tests 2018-03-03 14:59:40 +00:00			For more information about this error, try `rustc --explain E0004`.