-
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
empty_docs
triggered in proc-macros
#12377
Comments
There are a few additionaly warnings because of rust-lang/rust-clippy#12377, which is a nightly-only bug that will hopefully be fixed.
There are a few additional warnings because of rust-lang/rust-clippy#12377, which is a nightly-only bug that will hopefully be fixed.
There are a few additional warnings because of rust-lang/rust-clippy#12377, which is a nightly-only bug that will hopefully be fixed.
There are a few additional warnings because of rust-lang/rust-clippy#12377, which is a nightly-only bug that will hopefully be fixed.
@rustbot claim |
I'm still getting this problem, even on the new beta release. They show up in cli/src/template_parser.rs and lib/src/revset.rs of https://github.com/martinvonz/jj/tree/f865c1bc5d96f609d2919d559de045dda8256c7c. (There are also many additional rustc 1.78.0-beta.1 (efd9d2df1 2024-03-18) Update: I'm also getting the same behavior with the latest nightly: rustc 1.79.0-nightly (3c85e56 2024-03-18) |
There are still some warnings from (seemingly) clippy bugs. Quoting myself from Discord: > PSA: the latest beta cargo clippy (from Rust 1.78) has some problems > that affect jj: rust-lang/rust-clippy#12467 > and rust-lang/rust-clippy#12377. You could > disable clippy::assigning_clones and clippy::empty_docs as a workaround. > VS Code can disable them in rust-analyzer, you can also use > https://github.com/ericseppanen/cargo-cranky (you can put Cranky.toml in > the per-user gitignore).
The fix isn't on nightly yet (clippy is only sync'd with upstream every two weeks, I believe the next sync happens on the 21st), so you'll have to wait a bit longer, or you could try to run clippy master locally on your project to confirm that this is fixed (or isn't fixed). |
I see, thanks for letting me know! Will the fix be backported to 1.78 stable? I'm not sure I know how to run the master clippy. I thought that was what nightly was for... |
The easiest way is cloning this repository, cd'ing into it and running |
Thanks! Indeed, that doesn't seem to trigger |
There are still some warnings from (seemingly) clippy bugs. Quoting myself from Discord: > PSA: the latest beta cargo clippy (from Rust 1.78) has some problems > that affect jj: rust-lang/rust-clippy#12467 > and rust-lang/rust-clippy#12377. You could > disable clippy::assigning_clones and clippy::empty_docs as a workaround. > VS Code can disable them in rust-analyzer, you can also use > https://github.com/ericseppanen/cargo-cranky (you can put Cranky.toml in > the per-user gitignore).
superseeds #5248, sorry @drHuangMHT only saw yours now, can you review this one? https://github.com/libp2p/rust-libp2p/actions/runs/8377129630/job/22938498078?pr=5253#step:6:843 is a bug, see [here](rust-lang/rust-clippy#12377) Thanks! Pull-Request: #5253.
superseeds #5248, sorry @drHuangMHT only saw yours now, can you review this one? https://github.com/libp2p/rust-libp2p/actions/runs/8377129630/job/22938498078?pr=5253#step:6:843 is a bug, see [here](rust-lang/rust-clippy#12377) Thanks! Pull-Request: #5253.
The many 'empty doc comment' warnings are a bug in Clippy: rust-lang/rust-clippy#12377
The many 'empty doc comment' warnings are a bug in Clippy: rust-lang/rust-clippy#12377
rust-lang/rust-clippy#12377 ``` error: empty doc comment --> openrr-plugin/src/gen/proxy.rs:10:1 | 10 | #[sabi_trait] | ^^^^^^^^^^^^^ | = help: consider removing or filling it = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#empty_docs = note: `-D clippy::empty-docs` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(clippy::empty_docs)]` = note: this error originates in the attribute macro `sabi_trait` (in Nightly builds, run with -Z macro-backtrace for more info) ```
rust-lang/rust-clippy#12377 ``` error: empty doc comment --> openrr-plugin/src/gen/proxy.rs:10:1 | 10 | #[sabi_trait] | ^^^^^^^^^^^^^ | = help: consider removing or filling it = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#empty_docs = note: `-D clippy::empty-docs` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(clippy::empty_docs)]` = note: this error originates in the attribute macro `sabi_trait` (in Nightly builds, run with -Z macro-backtrace for more info) ```
rust-lang/rust-clippy#12377 ``` error: empty doc comment --> openrr-plugin/src/gen/proxy.rs:10:1 | 10 | #[sabi_trait] | ^^^^^^^^^^^^^ | = help: consider removing or filling it = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#empty_docs = note: `-D clippy::empty-docs` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(clippy::empty_docs)]` = note: this error originates in the attribute macro `sabi_trait` (in Nightly builds, run with -Z macro-backtrace for more info) ```
Summary
The just newly introduced #12342 is triggered in proc-macros.
Lint Name
empty_docs
Reproducer
I tried this code:
I saw this happen:
I expected to see this happen:
The lint not to trigger.
Version
Additional Labels
@rustbot label +T-macros
The text was updated successfully, but these errors were encountered: