-
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 [absolute_paths
]
#11003
New lint [absolute_paths
]
#11003
Conversation
r? @Alexendoo (rustbot has picked a reviewer for you, use r? to override) |
☔ The latest upstream changes (presumably #10884) made this pull request unmergeable. Please resolve the merge conflicts. |
Would you like to take a look at this one @blyxyas? (If you have a bunch on your plate already please say so) |
Yeah, I'll take a look! |
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 we should have an option to enable std
uses with any levels. For example, in my projects I usually leave std
functions with their absolute paths to show that they are from the standard library.
ra actually colors such functions differently, not sure whether that works across all IDEs though |
This is the first time I hear about this 🤯 |
Hmm weird. I'm using one dark pro with vscode (yes, I'm boring) and I see this: What theme are you using? I'm on a slightly older pre-release version as I tried seeing if a newer version caused a couple issues (it did not). I'll see if that's the cause (but I don't think so). e: one dark pro supports |
Just updated VSCode to the latest version, changed theme to One Dark Pro and reloaded RA. It works now. |
Yeah I still agree adding a configuration option is a good idea |
☔ The latest upstream changes (presumably #11020) made this pull request unmergeable. Please resolve the merge conflicts. |
☔ The latest upstream changes (presumably #10788) made this pull request unmergeable. Please resolve the merge conflicts. |
@rustbot label: -I-nominated |
☔ The latest upstream changes (presumably #11095) made this pull request unmergeable. Please resolve the merge conflicts. |
f8a4ec2
to
38b871f
Compare
☔ The latest upstream changes (presumably #11140) made this pull request unmergeable. Please resolve the merge conflicts. |
You can only pass flags to rust-clippy/.cargo/config.toml Lines 2 to 4 in 9f0cbfd
|
Interesting, I'll keep that in mind, though I'm not sure why Nevermind |
Oh and remember to update the config value names if the lint name changes |
c5e0a11
to
c1028af
Compare
☔ The latest upstream changes (presumably #11107) made this pull request unmergeable. Please resolve the merge conflicts. |
Thanks! r=me,blyxyas with squashed commits |
f8b418d
to
8d23767
Compare
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.
oop, actually a couple things but then it's good
The commit message calls it absolute_symbol_paths
still also
👍 @bors r=Alexendoo,blyxyas |
☀️ Test successful - checks-action_dev_test, checks-action_remark_test, checks-action_test |
Closes #10568
Maybe we should make the max segments allowed a configuration option? I see quite a bit of 3-segment paths in clippy, and while I think only really
<mod/type>::<item>
or<item>
should be (usually) used but anything above may be too widespread 😕PS, despite this being "max segments allowed" it only lints if it's absolute, as is the point of the lint, e.g.,
std::io::ErrorKind::etc
is linted butio::ErrorKind::NotFound::etc
isn'tchangelog: New lint [
absolute_paths
]