Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Different compiler versions disagree on whether failure_derive macro is used or not #56716

Open
mulkieran opened this issue Dec 11, 2018 · 0 comments
Open

Different compiler versions disagree on whether failure_derive macro is used or not #56716

mulkieran opened this issue Dec 11, 2018 · 0 comments
Labels
A-diagnostics Area: Messages for errors, warnings, and lints C-enhancement Category: An issue proposing an enhancement or a PR with one. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.

Comments

@mulkieran
Copy link

This leads to some compatibility issues. The code I have now compiles on 1.25.0 and 1.28.0 but reports an unused [macro_use] import for 1.31.0. https://travis-ci.org/stratis-storage/devicemapper-rs/jobs/466549505. Is this a bug in Rust, or something about the behavior of the failure_derive crate?

Duplicate issue in failure crate: rust-lang-deprecated/failure#278, because I'm hoping someone has a hunch about which it is.
@cuviper cuviper added the A-diagnostics Area: Messages for errors, warnings, and lints label Dec 11, 2018
@crlf0710 crlf0710 added C-enhancement Category: An issue proposing an enhancement or a PR with one. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels Jun 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-diagnostics Area: Messages for errors, warnings, and lints C-enhancement Category: An issue proposing an enhancement or a PR with one. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@cuviper @crlf0710 @mulkieran