about summary refs log tree commit diff
path: root/src/test/ui/iterators/iter-count-overflow-debug.rs
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2020-11-27 22:34:59 +0000
committerbors <bors@rust-lang.org>2020-11-27 22:34:59 +0000
commitfd6b5376b723e22e3d98542e2e693d2717700900 (patch)
tree462f3e93b54fb4f045e34612e90531585a2985e8 /src/test/ui/iterators/iter-count-overflow-debug.rs
parent6a889570e46c03d7b156ec08f3f4cb4d145924a3 (diff)
parent941c6ac1a26b6cc572279b0ac22d89fefb63c086 (diff)
downloadrust-fd6b5376b723e22e3d98542e2e693d2717700900.tar.gz
rust-fd6b5376b723e22e3d98542e2e693d2717700900.zip
Auto merge of #79284 - Nadrieril:constructor-module, r=varkor
Split match exhaustiveness into two files

I feel the constructor-related things in the `_match` module make enough sense on their own so I split them off. It makes `_match` feel less like a complicated mess. I'm not aware of PRs in progress against this module apart from my own so hopefully I'm not annoying too many people.
I have a lot of questions about the conventions in naming and modules around the compiler. Like, why is the module named `_match`? Could I rename it to `usefulness` maybe? Should `deconstruct_pat` be a submodule of `_match` since only `_match` uses it? Is it ok to move big piles of code around even if it makes git blame more difficult?

r? `@varkor`
`@rustbot` modify labels: +A-exhaustiveness-checking
Diffstat (limited to 'src/test/ui/iterators/iter-count-overflow-debug.rs')
0 files changed, 0 insertions, 0 deletions