diff options
| author | bors <bors@rust-lang.org> | 2024-01-26 00:17:00 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2024-01-26 00:17:00 +0000 |
| commit | e8d600fd23d7edfbee9ff7d99f732757f51e7a08 (patch) | |
| tree | 7f729d38e4d145c1152c5a03fddd41eba31ab318 /tests/debuginfo/enum-thinlto.rs | |
| parent | 50a067d7f84bdfac963669b69e9cd12b97d9a82f (diff) | |
| parent | adbc67664b98c2c5473a61b26019c86d8304dd46 (diff) | |
| download | rust-e8d600fd23d7edfbee9ff7d99f732757f51e7a08.tar.gz rust-e8d600fd23d7edfbee9ff7d99f732757f51e7a08.zip | |
Auto merge of #116167 - RalfJung:structural-eq, r=lcnr
remove StructuralEq trait The documentation given for the trait is outdated: *all* function pointers implement `PartialEq` and `Eq` these days. So the `StructuralEq` trait doesn't really seem to have any reason to exist any more. One side-effect of this PR is that we allow matching on some consts that do not implement `Eq`. However, we already allowed matching on floats and consts containing floats, so this is not new, it is just allowed in more cases now. IMO it makes no sense at all to allow float matching but also sometimes require an `Eq` instance. If we want to require `Eq` we should adjust https://github.com/rust-lang/rust/pull/115893 to check for `Eq`, and rule out float matching for good. Fixes https://github.com/rust-lang/rust/issues/115881
Diffstat (limited to 'tests/debuginfo/enum-thinlto.rs')
0 files changed, 0 insertions, 0 deletions