-
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
New lint [error_impl_error
]
#11107
New lint [error_impl_error
]
#11107
Conversation
r? @Jarcho (rustbot has picked a reviewer for you, use r? to override) |
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.
This really should be restricted to types exported from the current module. Module private types have none of the listed downsides.
Could be a configuration option |
☔ The latest upstream changes (presumably #10788) made this pull request unmergeable. Please resolve the merge conflicts. |
715d6bc
to
d680000
Compare
I was referring to not linting only for module-private types, not crate-private types. I doubt there's any use in having a config for this as they are unusual enough as is, and importing them would be even rarer as only sub-modules could do that. For types visible outside their own module I would still lint them as normal. If enough people want to ignore them, but still keep the lint otherwise then this can revisited, but I would rather not have a config option unless it's going to be useful. |
ah, yeah that would likely be rare enough that it wouldn't be too useful |
☔ The latest upstream changes (presumably #11140) made this pull request unmergeable. Please resolve the merge conflicts. |
09a7c64
to
44bb903
Compare
d68bbe6
to
ad86796
Compare
Also no longer lints non-exported types now
ad86796
to
19b0e84
Compare
Thank you. @bors r+ |
☀️ Test successful - checks-action_dev_test, checks-action_remark_test, checks-action_test |
Closes #11101
changelog: New lint [
error_impl_error
]