-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Don't suggest doc(hidden) or unstable variants in wildcard lint #7407
Changes from all commits
3e59563
38569c0
0ffba7a
fae7a09
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,8 @@ | ||
// Stripped down version of the ErrorKind enum of std | ||
#[non_exhaustive] | ||
pub enum ErrorKind { | ||
NotFound, | ||
PermissionDenied, | ||
#[doc(hidden)] | ||
Uncategorized, | ||
} |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,38 +1,44 @@ | ||
error: wildcard match will also match any future added variants | ||
--> $DIR/wildcard_enum_match_arm.rs:39:9 | ||
--> $DIR/wildcard_enum_match_arm.rs:42:9 | ||
| | ||
LL | _ => eprintln!("Not red"), | ||
| ^ help: try this: `Color::Green | Color::Blue | Color::Rgb(..) | Color::Cyan` | ||
| | ||
note: the lint level is defined here | ||
--> $DIR/wildcard_enum_match_arm.rs:3:9 | ||
--> $DIR/wildcard_enum_match_arm.rs:4:9 | ||
| | ||
LL | #![deny(clippy::wildcard_enum_match_arm)] | ||
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
|
||
error: wildcard match will also match any future added variants | ||
--> $DIR/wildcard_enum_match_arm.rs:43:9 | ||
--> $DIR/wildcard_enum_match_arm.rs:46:9 | ||
| | ||
LL | _not_red => eprintln!("Not red"), | ||
| ^^^^^^^^ help: try this: `_not_red @ Color::Green | _not_red @ Color::Blue | _not_red @ Color::Rgb(..) | _not_red @ Color::Cyan` | ||
|
||
error: wildcard match will also match any future added variants | ||
--> $DIR/wildcard_enum_match_arm.rs:47:9 | ||
--> $DIR/wildcard_enum_match_arm.rs:50:9 | ||
| | ||
LL | not_red => format!("{:?}", not_red), | ||
| ^^^^^^^ help: try this: `not_red @ Color::Green | not_red @ Color::Blue | not_red @ Color::Rgb(..) | not_red @ Color::Cyan` | ||
|
||
error: wildcard match will also match any future added variants | ||
--> $DIR/wildcard_enum_match_arm.rs:63:9 | ||
--> $DIR/wildcard_enum_match_arm.rs:66:9 | ||
| | ||
LL | _ => "No red", | ||
| ^ help: try this: `Color::Red | Color::Green | Color::Blue | Color::Rgb(..) | Color::Cyan` | ||
|
||
error: wildcard matches known variants and will also match future added variants | ||
--> $DIR/wildcard_enum_match_arm.rs:80:9 | ||
--> $DIR/wildcard_enum_match_arm.rs:83:9 | ||
| | ||
LL | _ => {}, | ||
| ^ help: try this: `ErrorKind::PermissionDenied | ErrorKind::ConnectionRefused | ErrorKind::ConnectionReset | ErrorKind::ConnectionAborted | ErrorKind::NotConnected | ErrorKind::AddrInUse | ErrorKind::AddrNotAvailable | ErrorKind::BrokenPipe | ErrorKind::AlreadyExists | ErrorKind::WouldBlock | ErrorKind::InvalidInput | ErrorKind::InvalidData | ErrorKind::TimedOut | ErrorKind::WriteZero | ErrorKind::Interrupted | ErrorKind::Other | ErrorKind::UnexpectedEof | ErrorKind::Unsupported | ErrorKind::OutOfMemory | _` | ||
| ^ help: try this: `ErrorKind::PermissionDenied | _` | ||
|
||
error: aborting due to 5 previous errors | ||
error: wildcard matches known variants and will also match future added variants | ||
--> $DIR/wildcard_enum_match_arm.rs:101:13 | ||
| | ||
LL | _ => (), | ||
| ^ help: try this: `Enum::B | _` | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I find it confusing that the lint suggests here to use the enum value in the same arm as the wildcard. That would mean that future additions would also run into this branch. It would be good to either add a note to explain why a wildcard has to be present here or to make the suggestion to have two arms like this: Enum::B => {},
_ => { /* Hidden values */ } Adding a note that the enum includes hidden, or unstable values would still be good. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. A |
||
|
||
error: aborting due to 6 previous errors | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think here it would be good to differentiate between the enums origin. It would make sense to me to also cover hidden/unstable variations if they originate from the same crate. (I couldn't find a check for that in the current implementation)
I'm also debating if that should be configurable, but I believe there is no real reason for that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this has to be done in this PR. I like this idea though. Can you open a good-first-issue issue for this, please?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cc: #7419