diff options
| author | bors <bors@rust-lang.org> | 2024-02-12 07:36:51 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2024-02-12 07:36:51 +0000 |
| commit | b7972e51024d1417422c933a6ff3caa370a92de5 (patch) | |
| tree | e196f895c0ca216dccdf8ae9325e3f80a2674727 /tests/codegen/src-hash-algorithm | |
| parent | c06ca6cff5af0fce63d4a28b33e5d244686cb442 (diff) | |
| parent | 43caf8323a25ab24898ca92e0ef959e45a8e0bf2 (diff) | |
| download | rust-b7972e51024d1417422c933a6ff3caa370a92de5.tar.gz rust-b7972e51024d1417422c933a6ff3caa370a92de5.zip | |
Auto merge of #16533 - Nadrieril:update-pat-ana, r=HKalbasi
Update to latest `rustc_pattern_analysis` Here I go again. Two improvements this time. 1. I've removed the need for an arena for patterns. Turns out this wasn't gaining any performance on the rustc side so may as well allocate normally. 2. I've added a clean error path when types don't match, so rustc_pattern_analysis should never panic except internal logic errors. For now `cx.bug()` calls `never!()` but I'm not sure what `never!()` does. Does it display anything to the user? Otherwise a `debug!()` should be sufficient. Point 2 should fix https://github.com/rust-lang/rust-analyzer/issues/15883 but I haven't tested it because I'm not sure how to reproduce. Could someone give me pointers as to how to write a test for the pattern code?
Diffstat (limited to 'tests/codegen/src-hash-algorithm')
0 files changed, 0 insertions, 0 deletions