diff options
| author | Aaron Hill <aa1ronham@gmail.com> | 2020-01-25 15:30:19 -0500 |
|---|---|---|
| committer | Aaron Hill <aa1ronham@gmail.com> | 2020-02-04 13:20:47 -0500 |
| commit | 302f8c97ea92d010f39a19563e8881a704c6f136 (patch) | |
| tree | 8d51862b1f221c56c07e2257a3af1f28699568c8 /src/liballoc/alloc | |
| parent | 126ad2b813010447807b0593a80bc6c04962e7ea (diff) | |
| download | rust-302f8c97ea92d010f39a19563e8881a704c6f136.tar.gz rust-302f8c97ea92d010f39a19563e8881a704c6f136.zip | |
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`
Diffstat (limited to 'src/liballoc/alloc')
0 files changed, 0 insertions, 0 deletions