rust/tests/ui/issues/issue-14091-2.stderr

error[E0600]: cannot apply unary operator `!` to type `BytePos`
  --> $DIR/issue-14091-2.rs:15:5
   |
LL |     assert!(x, x);
   |     ^^^^^^^^^^^^^ cannot apply unary operator `!`
   |
note: an implementation of `Not` might be missing for `BytePos`
  --> $DIR/issue-14091-2.rs:6:1
   |
LL | pub struct BytePos(pub u32);
   | ^^^^^^^^^^^^^^^^^^ must implement `Not`
note: the trait `Not` must be implemented
  --> $SRC_DIR/core/src/ops/bit.rs:LL:COL
   = note: this error originates in the macro `assert` (in Nightly builds, run with -Z macro-backtrace for more info)

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0600`.
Move some `compile-fail` tests to `ui` 2018-07-15 16:11:54 -05:00			error[E0600]: cannot apply unary operator `!` to type `BytePos`
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/issue-14091-2.rs:15:5`
Move some `compile-fail` tests to `ui` 2018-07-15 16:11:54 -05:00			`\|`
			`LL \| assert!(x, x);`
Bless tests 2021-10-14 13:28:28 -05:00			\| ^^^^^^^^^^^^^ cannot apply unary operator `!`
Move some `compile-fail` tests to `ui` 2018-07-15 16:11:54 -05:00			`\|`
Consider unfulfilled obligations in binop errors When encountering a binop where the types would have been accepted, if all the predicates had been fulfilled, include information about the predicates and suggest appropriate `#[derive]`s if possible. Point at trait(s) that needs to be `impl`emented. 2021-09-28 09:48:54 -05:00			note: an implementation of `Not` might be missing for `BytePos`
			`--> $DIR/issue-14091-2.rs:6:1`
			`\|`
			`LL \| pub struct BytePos(pub u32);`
Shorten def_span for more items. 2022-02-13 09:27:59 -06:00			\| ^^^^^^^^^^^^^^^^^^ must implement `Not`
Inform the user which trait is meant in the diagnostic itself instead of relying on the span making it obvious 2022-12-12 05:55:46 -06:00			note: the trait `Not` must be implemented
Consider unfulfilled obligations in binop errors When encountering a binop where the types would have been accepted, if all the predicates had been fulfilled, include information about the predicates and suggest appropriate `#[derive]`s if possible. Point at trait(s) that needs to be `impl`emented. 2021-09-28 09:48:54 -05:00			`--> $SRC_DIR/core/src/ops/bit.rs:LL:COL`
Show macro name in 'this error originates in macro' message When there are multiple macros in use, it can be difficult to tell which one was responsible for producing an error. 2021-02-13 13:52:25 -06:00			= note: this error originates in the macro `assert` (in Nightly builds, run with -Z macro-backtrace for more info)
Move some `compile-fail` tests to `ui` 2018-07-15 16:11:54 -05:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 09:44:16 -06:00			`error: aborting due to 1 previous error`
Move some `compile-fail` tests to `ui` 2018-07-15 16:11:54 -05:00
			For more information about this error, try `rustc --explain E0600`.