rustc_marker_type built in attribute created to have certain marker types not trigger dead code warnings from clippy#154978
Conversation
|
Some changes occurred in compiler/rustc_hir/src/attrs cc @jdonszelmann, @JonathanBrouwer Some changes occurred in compiler/rustc_passes/src/check_attr.rs cc @jdonszelmann, @JonathanBrouwer Some changes occurred in src/tools/clippy cc @rust-lang/clippy |
|
r? @davidtwco rustbot has assigned @davidtwco. Use Why was this reviewer chosen?The reviewer was selected based on:
|
|
This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed. Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers. |
This comment has been minimized.
This comment has been minimized.
218306c to
2206c25
Compare
260b712 to
55627ab
Compare
This comment has been minimized.
This comment has been minimized.
55627ab to
7b574a6
Compare
This comment has been minimized.
This comment has been minimized.
…ypes not trigger dead code warnings from clippy
7b574a6 to
60f81d1
Compare
|
The job Click to see the possible cause of the failure (guessed by this bot) |
This PR fixes the issue on
PhantomPinnedtriggering field is never read warning by clippy through a built in attribute calledrustc_marker_type.A few questions I have are:
Phantom*types?Note: This is my first time contributing to the compiler side of Rust repos, so I'm unsure if I'm doing anything wrong with making a built in attribute. I'm just going based off my intuition from go to references in my IDE on what everything is doing.
cc @clarfonthey