Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign up`try!()` macro is generating the `unused_qualifications` lint #37345
Comments
This comment has been minimized.
This comment has been minimized.
|
I don't think adding an allow in @jseyfried Do you know anything about this? |
This comment has been minimized.
This comment has been minimized.
|
I'm not aware of any recent changes that would cause new warnings / regressions, but I could disable the lint for macro-expanded paths easily. |
TheNeikos
added a commit
to TheNeikos/rustbreak
that referenced
this issue
Oct 22, 2016
This comment has been minimized.
This comment has been minimized.
|
Introduced between @jseyfried: This could probably be a side effect of #37213. |
TimNN
added
A-macros
regression-from-stable-to-nightly
A-compiler
T-compiler
and removed
A-compiler
labels
Oct 22, 2016
TheNeikos
added a commit
to TheNeikos/rustbreak
that referenced
this issue
Oct 22, 2016
This comment has been minimized.
This comment has been minimized.
bors
added a commit
that referenced
this issue
Oct 26, 2016
bors
closed this
in
#37361
Oct 26, 2016
This comment has been minimized.
This comment has been minimized.
|
Totally just got bitten by this in winapi, can't wait for the next nightly. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
bluss commentedOct 22, 2016
The macro should not cause warnings in the user's code. This seems to show up due to other changes.
Seen here: https://internals.rust-lang.org/t/regression-report-stable-2016-10-20-vs-nightly-2016-10-21/4255
The lint is allow by default, but some configurations will enable it.