error: cannot have both #[error(transparent)] and a display attribute
--> tests/test_transparent.rs:51:5
|
51 | #[error("this failed: {0}_{1}")]
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
error[E0381]: used binding `ahead` is possibly-uninitialized
--> impl/src/fmt.rs:187:30
|
182 | let ahead;
| ----- binding declared here but left uninitialized
183 | if *syn_full.get_or_insert_with(is_syn_full) && {
184 | ahead = input.fork();
| -----
| |
| binding initialized here in some conditions
| binding initialized here in some conditions
...
187 | input.advance_to(&ahead);
| ^^^^^^ `ahead` used here but it is possibly-uninitialized
error[E0599]: `test_no_bound_on_named_fmt::Error<DebugOnly>` doesn't implement `std::fmt::Display`
--> tests/test_generics.rs:173:22
|
168 | struct Error<T> {
| --------------- method `to_string` not found for this struct because it doesn't satisfy `_: Display` or `_: ToString`
...
173 | assert_eq!(error.to_string(), "...");
| ^^^^^^^^^ `test_no_bound_on_named_fmt::Error<DebugOnly>` cannot be formatted with the default formatter
|
= note: the following trait bounds were not satisfied:
`test_no_bound_on_named_fmt::Error<DebugOnly>: std::fmt::Display`
which is required by `test_no_bound_on_named_fmt::Error<DebugOnly>: ToString`
= note: in format strings you may be able to use `{:?}` (or {:#?} for pretty-print) instead
note: the trait `std::fmt::Display` must be implemented
--> $RUSTUP_HOME/toolchains/nightly-aarch64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/fmt/mod.rs:727:1
|
727 | pub trait Display {
| ^^^^^^^^^^^^^^^^^
= help: items from traits can only be used if the trait is implemented and in scope
= note: the following trait defines an item `to_string`, perhaps you need to implement it:
candidate #1: `ToString`
Without r#Backtrace:
error[E0308]: mismatched types
--> tests/test_backtrace.rs:42:14
|
42 | #[derive(Error, Debug)]
| ^^^^^
| |
| expected `std::backtrace::Backtrace`, found `not_backtrace::Backtrace`
| arguments to this method are incorrect
|
= note: `not_backtrace::Backtrace` and `std::backtrace::Backtrace` have similar names, but are actually distinct types
note: `not_backtrace::Backtrace` is defined in the current crate
--> tests/test_backtrace.rs:26:9
|
26 | pub struct Backtrace;
| ^^^^^^^^^^^^^^^^^^^^
note: `std::backtrace::Backtrace` is defined in crate `std`
--> $RUSTUP_HOME/toolchains/nightly-aarch64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/backtrace.rs:108:1
|
108 | pub struct Backtrace {
| ^^^^^^^^^^^^^^^^^^^^
note: method defined here
--> $RUSTUP_HOME/toolchains/nightly-aarch64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/error.rs:607:12
|
607 | pub fn provide_ref<T: ?Sized + 'static>(&mut self, value: &'a T) -> &mut Self {
| ^^^^^^^^^^^
= note: this error originates in the derive macro `Error` (in Nightly builds, run with -Z macro-backtrace for more info)
Without r#source:
error[E0599]: the method `as_dyn_error` exists for type `char`, but its trait bounds were not satisfied
--> tests/test_source.rs:72:9
|
72 | source: char,
| ^^^^^^ method cannot be called on `char` due to unsatisfied trait bounds
|
= note: the following trait bounds were not satisfied:
`char: std::error::Error`
which is required by `char: AsDynError<'_>`
