Uh oh!
There was an error while loading. Please reload this page.
Initial implementation of or-pattern usefulness checking - #66612
Conversation
This comment has been minimized.
This comment has been minimized.
Centril
commented
Nov 21, 2019
@bors try @rust-timer queue |
rust-timer
commented
Nov 21, 2019
Awaiting bors try build completion |
This comment has been minimized.
This comment has been minimized.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
bors
commented
Nov 22, 2019
Initial implementation of or-pattern usefulness checking The title says it all. I'd like to request a perf run on that, hopefully this doesn't kill performance too much. cc #54883
This comment has been minimized.
This comment has been minimized.
bors
commented
Nov 23, 2019
☀️ Try build successful - checks-azure |
rust-timer
commented
Nov 23, 2019
Queued 320df38 with parent 5fa0af2, future comparison URL. |
rust-timer
commented
Nov 23, 2019
Finished benchmarking try commit 320df38, comparison URL. |
| } | ||
| match (0u8,) { | ||
| (1 | 1,) => {} // redundancy not detected for now |
There was a problem hiding this comment.
I assume you have plans for this somehow... =P
There was a problem hiding this comment.
I do ^^. This is actually necessary if we want to remove the hack for top-level or-patterns and keep the same diagnostics. I'll have a follow-up PR up soon
varkor
left a comment
There was a problem hiding this comment.
Changes look good — r=me with the nits fixed.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Co-Authored-By: varkor <github@varkor.com>
varkor
commented
Nov 30, 2019
Great, thank you very much for working on this! @bors r+ |
bors
commented
Nov 30, 2019
📌 Commit 0f4c5fb has been approved by |
bors
commented
Nov 30, 2019
🌲 The tree is currently closed for pull requests below priority 1000, this pull request will be tested once the tree is reopened |
…rkor Initial implementation of or-pattern usefulness checking The title says it all. I'd like to request a perf run on that, hopefully this doesn't kill performance too much. cc rust-lang#54883
Rollup of 9 pull requests Successful merges: - #66612 (Initial implementation of or-pattern usefulness checking) - #66705 (Atomic as_mut_ptr) - #66759 (impl TrustedLen for vec::Drain) - #66858 (Use LLVMAddAnalysisPasses instead of Rust's wrapper) - #66870 (SimplifyArmIdentity only for locals with the same type) - #66883 (rustc_typeck: gate AnonConst's generics on feature(const_generics).) - #66889 (Make python-generated source files compatible with rustfmt) - #66894 (Remove unneeded prelude imports in libcore tests) - #66895 (Feature gating *declarations* => new crate `rustc_feature`) Failed merges: - #66905 (rustc_plugin: Remove some remaining plugin features) r? @ghost
bors
commented
Dec 1, 2019
☔ The latest upstream changes (presumably #66908) made this pull request unmergeable. Please resolve the merge conflicts. |
Nadrieril
commented
Dec 1, 2019
I'm confused, bors merged the PR and then detected a conflict with itself ? Is that a false positive from bors or do I need to rebase on master ? |
Centril
commented
Dec 1, 2019
That's a false positive from the buggy bors; no need to do anything. |
Remove hack for top-level or-patterns in match checking Follow-up to rust-lang#66612. Or-patterns are now truly first-class in match checking. As a side-effect, redundant subpatterns are linted as such, making the `unreachable_patterns` lint a bit more general. cc rust-lang#54883 r? @varkor
Remove hack for top-level or-patterns in match checking Follow-up to rust-lang#66612. Or-patterns are now truly first-class in match checking. As a side-effect, redundant subpatterns are linted as such, making the `unreachable_patterns` lint a bit more general. cc rust-lang#54883 r? @varkor
mark-i-m
commented
Dec 5, 2019
😱 How dare you insult the @bors 💥 HE SEES ALLLLLLLLLL |
The title says it all.
I'd like to request a perf run on that, hopefully this doesn't kill performance too much.
cc #54883