rust/tests/ui/traits/overlap-not-permitted-for-builtin-trait.stderr

error[E0119]: conflicting implementations of trait `Send` for type `MyStruct`
  --> $DIR/overlap-not-permitted-for-builtin-trait.rs:7:1
   |
LL | impl !Send for MyStruct {}
   | ----------------------- first implementation here
LL | impl !Send for MyStruct {}
   | ^^^^^^^^^^^^^^^^^^^^^^^ conflicting implementation for `MyStruct`

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0119`.
Don't print full paths in overlap errors 2022-11-10 04:21:11 +00:00			error[E0119]: conflicting implementations of trait `Send` for type `MyStruct`
Remove the `overlapping_marker_traits` feature See #29864 This has been replaced by `#[feature(marker_trait_attr)]` A few notes: * Due to PR #68057 not yet being in the bootstrap compiler, it's necessary to continue using `#![feature(overlapping_marker_traits)]` under `#[cfg(bootstrap)]` to work around type inference issues. * I've updated tests that used `overlapping_marker_traits` to now use `marker_trait_attr` where applicable The test `src/test/ui/overlap-marker-trait.rs` doesn't make any sense now that `overlapping_marker_traits`, so I removed it. The test `src/test/ui/traits/overlap-permitted-for-marker-traits-neg.rs` now fails, since it's no longer possible to have multiple overlapping negative impls of `Send`. I believe that this is the behavior we want (assuming that `Send` is not going to become a `#[marker]` trait, so I renamed the test to `overlap-permitted-for-marker-traits-neg` 2020-01-25 20:30:19 +00:00			`--> $DIR/overlap-not-permitted-for-builtin-trait.rs:7:1`
			`\|`
			`LL \| impl !Send for MyStruct {}`
			`\| ----------------------- first implementation here`
			`LL \| impl !Send for MyStruct {}`
			\| ^^^^^^^^^^^^^^^^^^^^^^^ conflicting implementation for `MyStruct`

Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 15:44:16 +00:00			`error: aborting due to 1 previous error`
Remove the `overlapping_marker_traits` feature See #29864 This has been replaced by `#[feature(marker_trait_attr)]` A few notes: * Due to PR #68057 not yet being in the bootstrap compiler, it's necessary to continue using `#![feature(overlapping_marker_traits)]` under `#[cfg(bootstrap)]` to work around type inference issues. * I've updated tests that used `overlapping_marker_traits` to now use `marker_trait_attr` where applicable The test `src/test/ui/overlap-marker-trait.rs` doesn't make any sense now that `overlapping_marker_traits`, so I removed it. The test `src/test/ui/traits/overlap-permitted-for-marker-traits-neg.rs` now fails, since it's no longer possible to have multiple overlapping negative impls of `Send`. I believe that this is the behavior we want (assuming that `Send` is not going to become a `#[marker]` trait, so I renamed the test to `overlap-permitted-for-marker-traits-neg` 2020-01-25 20:30:19 +00:00
			For more information about this error, try `rustc --explain E0119`.