rust/tests/ui/on-unimplemented/no-debug.stderr

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

error[E0277]: `Bar` doesn't implement `Debug`
  --> $DIR/no-debug.rs:10:32
   |
LL |     println!("{:?} {:?}", Foo, Bar);
   |                                ^^^ `Bar` cannot be formatted using `{:?}` because it doesn't implement `Debug`
   |
   = help: the trait `Debug` is not implemented for `Bar`
   = note: this error originates in the macro `$crate::format_args_nl` which comes from the expansion of the macro `println` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0277]: `Foo` doesn't implement `std::fmt::Display`
  --> $DIR/no-debug.rs:11:23
   |
LL |     println!("{} {}", Foo, Bar);
   |                       ^^^ `Foo` cannot be formatted with the default formatter
   |
   = help: the trait `std::fmt::Display` is not implemented for `Foo`
   = note: in format strings you may be able to use `{:?}` (or {:#?} for pretty-print) instead
   = note: this error originates in the macro `$crate::format_args_nl` which comes from the expansion of the macro `println` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0277]: `Bar` doesn't implement `std::fmt::Display`
  --> $DIR/no-debug.rs:11:28
   |
LL |     println!("{} {}", Foo, Bar);
   |                            ^^^ `Bar` cannot be formatted with the default formatter
   |
   = help: the trait `std::fmt::Display` is not implemented for `Bar`
   = note: in format strings you may be able to use `{:?}` (or {:#?} for pretty-print) instead
   = note: this error originates in the macro `$crate::format_args_nl` which comes from the expansion of the macro `println` (in Nightly builds, run with -Z macro-backtrace for more info)

error: aborting due to 4 previous errors

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 07:40:56 +00:00			error[E0277]: `Foo` doesn't implement `Debug`
Remove licenses 2018-12-25 15:56:47 +00:00			`--> $DIR/no-debug.rs:10:27`
Add filter to detect local crates for rustc_on_unimplemented 2018-01-20 09:33:39 +00:00			`\|`
Update UI tests 2018-02-23 00:42:32 +00:00			`LL \| println!("{:?} {:?}", Foo, Bar);`
Suggest more helpful formatting string 2018-05-04 11:43:52 +00:00			\| ^^^ `Foo` cannot be formatted using `{:?}`
Add filter to detect local crates for rustc_on_unimplemented 2018-01-20 09:33:39 +00:00			`\|`
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			= help: the trait `Debug` is not implemented for `Foo`
Change Debug unimplemented message per request 2021-06-22 07:38:31 +00:00			= note: add `#[derive(Debug)]` to `Foo` or manually `impl Debug for Foo`
Mention first and last macro in backtrace 2022-06-21 02:25:52 +00:00			= note: this error originates in the macro `$crate::format_args_nl` which comes from the expansion of the macro `println` (in Nightly builds, run with -Z macro-backtrace for more info)
Suggest derivable trait on E0277 2022-03-31 14:58:45 +00:00			help: consider annotating `Foo` with `#[derive(Debug)]`
			`\|`
Tweak output for 'add line' suggestion 2023-03-18 02:18:39 +00:00			`LL + #[derive(Debug)]`
			`LL \| struct Foo;`
Suggest derivable trait on E0277 2022-03-31 14:58:45 +00:00			`\|`
Add filter to detect local crates for rustc_on_unimplemented 2018-01-20 09:33:39 +00:00
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			error[E0277]: `Bar` doesn't implement `Debug`
Remove licenses 2018-12-25 15:56:47 +00:00			`--> $DIR/no-debug.rs:10:32`
Add filter to detect local crates for rustc_on_unimplemented 2018-01-20 09:33:39 +00:00			`\|`
Update UI tests 2018-02-23 00:42:32 +00:00			`LL \| println!("{:?} {:?}", Foo, Bar);`
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			\| ^^^ `Bar` cannot be formatted using `{:?}` because it doesn't implement `Debug`
Add filter to detect local crates for rustc_on_unimplemented 2018-01-20 09:33:39 +00:00			`\|`
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			= help: the trait `Debug` is not implemented for `Bar`
Mention first and last macro in backtrace 2022-06-21 02:25:52 +00:00			= note: this error originates in the macro `$crate::format_args_nl` which comes from the expansion of the macro `println` (in Nightly builds, run with -Z macro-backtrace for more info)
Add filter to detect local crates for rustc_on_unimplemented 2018-01-20 09:33:39 +00:00
			error[E0277]: `Foo` doesn't implement `std::fmt::Display`
Remove licenses 2018-12-25 15:56:47 +00:00			`--> $DIR/no-debug.rs:11:23`
Add filter to detect local crates for rustc_on_unimplemented 2018-01-20 09:33:39 +00:00			`\|`
Update UI tests 2018-02-23 00:42:32 +00:00			`LL \| println!("{} {}", Foo, Bar);`
Suggest more helpful formatting string 2018-05-04 11:43:52 +00:00			\| ^^^ `Foo` cannot be formatted with the default formatter
Add filter to detect local crates for rustc_on_unimplemented 2018-01-20 09:33:39 +00:00			`\|`
			= help: the trait `std::fmt::Display` is not implemented for `Foo`
Suggest more helpful formatting string 2018-05-04 11:43:52 +00:00			= note: in format strings you may be able to use `{:?}` (or {:#?} for pretty-print) instead
Mention first and last macro in backtrace 2022-06-21 02:25:52 +00:00			= note: this error originates in the macro `$crate::format_args_nl` which comes from the expansion of the macro `println` (in Nightly builds, run with -Z macro-backtrace for more info)
Add filter to detect local crates for rustc_on_unimplemented 2018-01-20 09:33:39 +00:00
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			error[E0277]: `Bar` doesn't implement `std::fmt::Display`
Remove licenses 2018-12-25 15:56:47 +00:00			`--> $DIR/no-debug.rs:11:28`
Add filter to detect local crates for rustc_on_unimplemented 2018-01-20 09:33:39 +00:00			`\|`
Update UI tests 2018-02-23 00:42:32 +00:00			`LL \| println!("{} {}", Foo, Bar);`
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			\| ^^^ `Bar` cannot be formatted with the default formatter
Add filter to detect local crates for rustc_on_unimplemented 2018-01-20 09:33:39 +00:00			`\|`
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			= help: the trait `std::fmt::Display` is not implemented for `Bar`
Suggest more helpful formatting string 2018-05-04 11:43:52 +00:00			= note: in format strings you may be able to use `{:?}` (or {:#?} for pretty-print) instead
Mention first and last macro in backtrace 2022-06-21 02:25:52 +00:00			= note: this error originates in the macro `$crate::format_args_nl` which comes from the expansion of the macro `println` (in Nightly builds, run with -Z macro-backtrace for more info)
Add filter to detect local crates for rustc_on_unimplemented 2018-01-20 09:33:39 +00:00
			`error: aborting due to 4 previous errors`

update tests 2018-03-03 14:59:40 +00:00			For more information about this error, try `rustc --explain E0277`.