-
Notifications
You must be signed in to change notification settings - Fork 13.3k
redundant_semicolon and clippy::no_effect tripped without emitting line numbers #63967
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
It can be reproduced by cloning that PR, removing the commit that adds the |
Check-in from compiler team: Marking as P-high " as this is a regression, though admittedly one without particularly serious consequences (the lint can always be allowed). @nathanwhit or @varkor, perhaps one of you can take a stab at this? Please claim the issue if you do start working on it (even if it's just to write mentoring instructions). |
Also, it'd be great to get a minimized version of the problem. Therefore, marking as E-needs-mvce. |
I'll work on this. Looking into it a bit, I think it has to do with the lint's interaction with custom proc macro attributes. Specifically, when the item |
…rkor Fix redundant semicolon lint interaction with proc macro attributes Fixes rust-lang#63967 and fixes rust-lang#63947, both of which were caused by the lint's changes to the parser interacting poorly with proc macro attributes and causing span information to be lost r? @varkor
…rkor Fix redundant semicolon lint interaction with proc macro attributes Fixes rust-lang#63967 and fixes rust-lang#63947, both of which were caused by the lint's changes to the parser interacting poorly with proc macro attributes and causing span information to be lost r? @varkor
…rkor Fix redundant semicolon lint interaction with proc macro attributes Fixes rust-lang#63967 and fixes rust-lang#63947, both of which were caused by the lint's changes to the parser interacting poorly with proc macro attributes and causing span information to be lost r? @varkor
…rkor Fix redundant semicolon lint interaction with proc macro attributes Fixes rust-lang#63967 and fixes rust-lang#63947, both of which were caused by the lint's changes to the parser interacting poorly with proc macro attributes and causing span information to be lost r? @varkor
…rkor Fix redundant semicolon lint interaction with proc macro attributes Fixes rust-lang#63967 and fixes rust-lang#63947, both of which were caused by the lint's changes to the parser interacting poorly with proc macro attributes and causing span information to be lost r? @varkor
@nathanwhit just in case you didn't see, the attempt to fix this with your PR #64387 failed the rollup, see #64387 (comment) |
Using nightly-2019-08-26.
In this TiKV PR we upgraded the compiler. Our tidb_query component tripped the redundant_semicolon lint (and seemingly in turn clippy::no_effect) but rustc/clippy did not tell us the line number.
I couldn't find the code that triggered the lint and had to just allow both for the whole crate.
This issue has been assigned to @nathanwhit via this comment.
The text was updated successfully, but these errors were encountered: