rust/tests/ui/pattern/usefulness/match-privately-empty.stderr

error[E0004]: non-exhaustive patterns: `Some(Private { misc: true, .. })` not covered
  --> $DIR/match-privately-empty.rs:13:11
   |
LL |     match private::DATA {
   |           ^^^^^^^^^^^^^ pattern `Some(Private { misc: true, .. })` not covered
   |
note: `Option<Private>` defined here
  --> $SRC_DIR/core/src/option.rs:LL:COL
  ::: $SRC_DIR/core/src/option.rs:LL:COL
   |
   = note: not covered
   = note: the matched value is of type `Option<Private>`
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern or an explicit pattern as shown
   |
LL ~         }) => {}
LL +         Some(Private { misc: true, .. }) => todo!()
   |

error: aborting due to previous error

For more information about this error, try `rustc --explain E0004`.
Moved compile-fail tests to ui tests. 2018-08-08 14:28:26 +02:00			error[E0004]: non-exhaustive patterns: `Some(Private { misc: true, .. })` not covered
tests: remove ignore directives from tests that mention core/alloc/std spans. 2020-04-01 04:10:13 +03:00			`--> $DIR/match-privately-empty.rs:13:11`
Moved compile-fail tests to ui tests. 2018-08-08 14:28:26 +02:00			`\|`
			`LL \| match private::DATA {`
			\| ^^^^^^^^^^^^^ pattern `Some(Private { misc: true, .. })` not covered
Remove trailing whitespace from error messages 2021-06-10 13:52:00 +02: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<Private>` 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`
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 10:40:56 +03:00			= note: the matched value is of type `Option<Private>`
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 or an explicit pattern as shown`
When finding a match expr with multiple arms that requires more, suggest it Given ```rust match Some(42) { Some(0) => {} Some(1) => {} } ``` suggest ```rust match Some(42) { Some(0) => {} Some(1) => {} None \| Some(_) => todo!(), } ``` 2021-12-16 02:28:09 +00:00			`\|`
			`LL ~ }) => {}`
			`LL + Some(Private { misc: true, .. }) => todo!()`
			`\|`
Moved compile-fail tests to ui tests. 2018-08-08 14:28:26 +02:00
			`error: aborting due to previous error`

			For more information about this error, try `rustc --explain E0004`.