-
Notifications
You must be signed in to change notification settings - Fork 12.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[DO NOT MERGE] crater: emit a warning if a match
is too complex
#121979
[DO NOT MERGE] crater: emit a warning if a match
is too complex
#121979
Conversation
Some changes occurred in exhaustiveness checking cc @Nadrieril |
match
is too complexmatch
is too complex
match
is too complexmatch
is too complex
@bors try |
…atch, r=<try> [DO NOT MERGE] crater: emit a warning if a `match` is too complex `@Nadrieril` suggested that it could be interesting to suggest to users when a `match` is too complex and that they should try to simplify it. The goal here is to find a threeshold where we will emit a warning suggesting to simplify a `match`. To do so, we'll run a crater run first and advise what to do from there. Currently the PR SHOULD NOT be merged as is and SHOULD NOT panic. r? `@Nadrieril`
☀️ Try build successful - checks-actions |
@craterbot run mode=check-only |
👌 Experiment ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
🚧 Experiment ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
🎉 Experiment
|
Experiment is a success, we can now turn it into a warning. |
@Nadrieril suggested that it could be interesting to suggest to users when a
match
is too complex and that they should try to simplify it.The goal here is to find a threeshold where we will emit a warning suggesting to simplify a
match
. To do so, we'll run a crater run first and advise what to do from there.Currently the PR SHOULD NOT be merged as is and SHOULD NOT panic.
r? @Nadrieril