-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Improve unexpected_cfgs lint when their is no value expected #94561
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
Conversation
r=me with formatting fixed #94561 (review) |
456496c
to
3be6ccd
Compare
CI pass but blocked on #94362 being merged first as some output files will change. |
#94362 has been merged. |
3be6ccd
to
92544f4
Compare
@bors r+ |
📌 Commit 92544f4 has been approved by |
☀️ Test successful - checks-actions |
Finished benchmarking commit (c8a49fc): comparison url. Summary: This benchmark run did not return any relevant results. 1 results were found to be statistically significant but too small to be relevant. If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression |
This pull-request improve the
unexpected_cfgs
when their is no value expected by suggesting to remove the value.I also took the liberty to special case it for
feature
as it seems wrong to suggest to remove the value when the problem is most probably the absence of value(s) and also the fact that it doesn't make sense to only havefeature
without a value.r? @petrochenkov