diff options
| author | Dylan DPC <dylan.dpc@gmail.com> | 2020-05-25 18:07:42 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-05-25 18:07:42 +0200 |
| commit | d5250c160a9bb463d08a0073962fdd68e33391b4 (patch) | |
| tree | cf5c67e1bf484b8713ea3ca0c07ba09a7b65c25d /src/libstd/sys/unix/stack_overflow.rs | |
| parent | ee6c0dae394f67b5286909704f8f0a608696c96c (diff) | |
| parent | a5a4ec98e20e4b863cfb2f6c44faa15824fce9f3 (diff) | |
| download | rust-d5250c160a9bb463d08a0073962fdd68e33391b4.tar.gz rust-d5250c160a9bb463d08a0073962fdd68e33391b4.zip | |
Rollup merge of #72153 - lcnr:exhaustively-match, r=pnkfelix
exhaustively check `ty::Kind` during structural match checking This was prone to errors as we may forget new kinds in the future. I am also not yet sure about some kinds. `ty::GeneratorWitness(..) | ty::Infer(_) | ty::Placeholder(_) | ty::UnnormalizedProjection(..) | ty::Bound(..)` might be unreachable here. We may want to forbid `ty::Projection`, similar to `ty::Param`. `ty::Opaque` seems fine afaict, should not be possible in a match atm. I believe `ty::Foreign` should not be structurally match, as I don't even know what that would actually mean. r? @pnkfelix cc @eddyb
Diffstat (limited to 'src/libstd/sys/unix/stack_overflow.rs')
0 files changed, 0 insertions, 0 deletions