rust/tests/ui/rfc-2361-dbg-macro/dbg-macro-requires-debug.stderr

error[E0277]: `NotDebug` doesn't implement `Debug`
  --> $DIR/dbg-macro-requires-debug.rs:6:23
   |
LL |     let _: NotDebug = dbg!(NotDebug);
   |                       ^^^^^^^^^^^^^^ `NotDebug` cannot be formatted using `{:?}`
   |
   = help: the trait `Debug` is not implemented for `NotDebug`
   = note: add `#[derive(Debug)]` to `NotDebug` or manually `impl Debug for NotDebug`
   = note: this error originates in the macro `$crate::format_args_nl` which comes from the expansion of the macro `dbg` (in Nightly builds, run with -Z macro-backtrace for more info)
help: consider annotating `NotDebug` with `#[derive(Debug)]`
   |
LL | #[derive(Debug)]
   |

error: aborting due to previous error

For more information about this error, try `rustc --explain E0277`.
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			error[E0277]: `NotDebug` doesn't implement `Debug`
stabilize std::dbg!(...) 2018-12-01 02:54:09 +01:00			`--> $DIR/dbg-macro-requires-debug.rs:6:23`
dbg_macro: Debug-required test. 2018-09-18 04:28:17 +02:00			`\|`
Update tests 2019-03-09 15:03:44 +03:00			`LL \| let _: NotDebug = dbg!(NotDebug);`
dbg_macro: Debug-required test. 2018-09-18 04:28:17 +02:00			\| ^^^^^^^^^^^^^^ `NotDebug` cannot be formatted using `{:?}`
			`\|`
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			= help: the trait `Debug` is not implemented for `NotDebug`
Change Debug unimplemented message per request 2021-06-22 00:38:31 -07:00			= note: add `#[derive(Debug)]` to `NotDebug` or manually `impl Debug for NotDebug`
Mention first and last macro in backtrace 2022-06-20 19:25:52 -07:00			= note: this error originates in the macro `$crate::format_args_nl` which comes from the expansion of the macro `dbg` (in Nightly builds, run with -Z macro-backtrace for more info)
Suggest derivable trait on E0277 2022-03-31 23:58:45 +09:00			help: consider annotating `NotDebug` with `#[derive(Debug)]`
			`\|`
			`LL \| #[derive(Debug)]`
			`\|`
dbg_macro: Debug-required test. 2018-09-18 04:28:17 +02:00
			`error: aborting due to previous error`

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