diff options
| author | Yuki Okushi <huyuumi.dev@gmail.com> | 2020-01-10 04:18:30 +0900 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-01-10 04:18:30 +0900 |
| commit | 68ae55bfac1a60fb3c9f45b3a223358ea598f56d (patch) | |
| tree | 0d1ddd542303d2ac2e00dcfe83fc09d18a4eeb92 /src/test/debuginfo/enum-thinlto.rs | |
| parent | 92bd267ba8d8d12cba15490c618628c1f3ea5ac5 (diff) | |
| parent | b82cd9f6391df865551bc6c756cc29a7993e39be (diff) | |
| download | rust-68ae55bfac1a60fb3c9f45b3a223358ea598f56d.tar.gz rust-68ae55bfac1a60fb3c9f45b3a223358ea598f56d.zip | |
Rollup merge of #67122 - petrochenkov:nodedup, r=estebank
Do not deduplicate diagnostics in UI tests Error reporting infrastructure deduplicates identical diagnostics with identical spans. While it's preferable to do this in "release"/"user-facing" mode, it sometimes brings [confusion](https://github.com/rust-lang/rust/pull/50682#issuecomment-390949878) and hides details that may be important during development. Do we run some passes multiple times when we could do it once? How many times we run them exactly? Can this number be large? Can the multiplied error construction be expensive? Can speculative checks be made cheaper if they don't report errors? *Relying* on this mechanism to deduplicate some specific error never looks like a proper solution to me personally. In this PR I attempt to disable this deduplication by applying `-Z deduplicate-diagnostics=no` to UI tests.
Diffstat (limited to 'src/test/debuginfo/enum-thinlto.rs')
0 files changed, 0 insertions, 0 deletions