diff options
| author | bors <bors@rust-lang.org> | 2020-06-18 21:50:45 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2020-06-18 21:50:45 +0000 |
| commit | 036b5fec49aa5d5143b83360442400d1e83ccefa (patch) | |
| tree | d1cb64d7c508890c8032bae0536fb59794c8c941 /src/libstd/sys/unix/stack_overflow.rs | |
| parent | e55d3f9c5213fe1a25366450127bdff67ad1eca2 (diff) | |
| parent | 3a1207f6883f799af13027ceb1715ff492382e87 (diff) | |
| download | rust-036b5fec49aa5d5143b83360442400d1e83ccefa.tar.gz rust-036b5fec49aa5d5143b83360442400d1e83ccefa.zip | |
Auto merge of #73446 - ecstatic-morse:issue-73431, r=pnkfelix
Make novel structural match violations not a `bug` Fixes (on master) #73431. Ideally, `CustomEq` would emit a strict subset of the structural match errors that are found by `search_for_structural_match_violation`, since it allows more cases due to value-based reasoning. However, const qualification is more conservative than `search_for_structural_match_violation` around associated constants, since qualification does not try to substitute type parameters. In the long term, we should probably make const qualification work for generic associated constants, but I don't like extending its capabilities even further. r? @pnkfelix
Diffstat (limited to 'src/libstd/sys/unix/stack_overflow.rs')
0 files changed, 0 insertions, 0 deletions