diff options
| author | Felix S. Klock II <pnkfelix@pnkfx.org> | 2021-01-23 00:54:19 -0500 |
|---|---|---|
| committer | Felix S. Klock II <pnkfelix@pnkfx.org> | 2021-02-01 17:08:37 -0500 |
| commit | 532332fa8f84b9b015baa2c065a9b1927259578c (patch) | |
| tree | 9e9c1d9fde8ff7ccf6bd4882a680cc85c82d66e7 /compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp | |
| parent | ff4665f45f846f82fd8046c50a0fe501b7f31665 (diff) | |
| download | rust-532332fa8f84b9b015baa2c065a9b1927259578c.tar.gz rust-532332fa8f84b9b015baa2c065a9b1927259578c.zip | |
Test exploring the interactions between all of the different kinds of method collisions I could imagine.
The different impls are all guarded by cfg-flags, and the revisions could be used to cover the full power-set of combinations. (I only included 20 of the possible 32 cases here; the null-set is not interesting, and the remaining 11 all yielded ambiguous method resolution errors which did not mix well with this testing strategy; I'm not trying to check UI for the resolution diagnostics; I'm trying to create checkpoint of current resolution semantics when compilation succeeds.)
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp')
0 files changed, 0 insertions, 0 deletions