Suppress some lints that trigger don't trigger in all cfg's#83
Suppress some lints that trigger don't trigger in all cfg's#83Alexhuszagh merged 1 commit intoAlexhuszagh:mainfrom
Conversation
|
The issue is |
Alexhuszagh
left a comment
There was a problem hiding this comment.
Please replace the #[allow(unused_macros)] changes to also allow unknown_lints, or #[allow(unknown_lints, unused_macros)].
Also please rebase to make sure input.rs doesn't have any conflicts, since I just submitted a similar patch to that file.
|
@Xiphoseer I'm planning a release this Wednesday to fix a bug present in #84 in the float writer, so I was wondering if these changes could be made prior to then to ensure no spurious warnings are present. If not, there are no issues, I would like to give you credit for your work so please take your own time. I appreciate all the work you've done. |
|
Right, I totally forgot about I've run the CI checks locally before submitting and they all went through. It looks to me like no CI check actually runs something like Also noticed something weird while testing this: The |
Incredible work, thank you for all your help with this. |
This
allowsa new nightly lint (rust-lang/rust#96150) on some macros that trigger because of how they interact withcfgattributes. From my point-of-view, it didn't make sense to replicate thosecfgin ancfg_attrhere. There's another case in mypatch-5branch, which might not be a false-positive like these ones.