diff options
| author | bors <bors@rust-lang.org> | 2022-06-30 14:51:58 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2022-06-30 14:51:58 +0000 |
| commit | 642084093a94228bd1fb4f61f249bfe9a28c6faf (patch) | |
| tree | c076173b22284b3ecd0273ab2de7dd205c903ba7 /src/test/codegen/src-hash-algorithm | |
| parent | 7f9c054686fb3e1af7acb7292e05462afc138981 (diff) | |
| parent | e417992674baf9635f816e520ee8c0d11150bfdb (diff) | |
| download | rust-642084093a94228bd1fb4f61f249bfe9a28c6faf.tar.gz rust-642084093a94228bd1fb4f61f249bfe9a28c6faf.zip | |
Auto merge of #12634 - iDawer:match-check.witnesses, r=flodiebold
feat: Show witnesses of non-exhaustiveness in `missing-match-arm` diagnostic Shamelessly copied from rustc. Thus reporting format is same. This extends public api `hir::diagnostics::MissingMatchArms` with `uncovered_patterns: String` field. It does not expose data for implementing a quick fix yet. ----- Worth to note: current implementation does not give a comprehensive list of missing patterns. Also mentioned in [paper](http://moscova.inria.fr/~maranget/papers/warn/warn.pdf): > One may think that algorithm I should make an additional effort to provide more > non-matching values, by systematically computing recursive calls on specialized > matrices when possible, and by returning a list of all pattern vectors returned by > recursive calls. We can first observe that it is not possible in general to supply the > users with all non-matching values, since the signature of integers is (potentially) > infinite.
Diffstat (limited to 'src/test/codegen/src-hash-algorithm')
0 files changed, 0 insertions, 0 deletions