-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Properly handle feature-gated lints #72694
Comments
This implementation plan looks good to me -- if you think @LeSeulArtichaut that you'd like to mentor the issue, maybe tag it with E-easy and E-mentor! I'd probably extend the description above with
|
Hi, I would like to take this up if possible. I'm new to contributing to rust |
Also, to show that you're working on an issue, you can send |
@rajatppn Are you still working on this? If not, I'd like to claim it. |
I'm also interested, looking for a first ticket |
I'll assign this to @OddCoincidence (who opened a PR) for triage purposes. @carsonmyers Good luck on finding a first issue! If you don't find anything, you can probably go in the Rust Zulip instance and ask for issues, |
… r=petrochenkov Properly handle feature-gated lints Closes rust-lang#72694
… r=petrochenkov Properly handle feature-gated lints Closes rust-lang#72694
At the moment, the
unsafe_op_in_unsafe_fn
lint is the only feature-gated lint. However, feature-gate checks are hard-coded for this lint. If more feature gated lints are be added in the future, having proper handling for feature-gated lint will be useful.Here is a suggested implementation plan:
feature_gate
field of typeOption<Symbol>
for therustc_session::lint::Lint
struct, which has aSome
value if the lint is feature-gated,None
otherwise.rustc_session::declare_lint!
macro to allow specifying the feature gate when applicable, akin tofuture_incompatible
.check_gated_link
should be enough.This issue has been assigned to @OddCoincidence via this comment.
The text was updated successfully, but these errors were encountered: