-
Notifications
You must be signed in to change notification settings - Fork 62
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
snafu-derive 0.4.2 broke #[doc(hidden)]
#139
Comments
Hi John, Can I suggest that you create a minimal reproducer - I think it would be trivial, but I've not got rust available at the moment, so can't whip one up myself. That way there will be something simple for developers to turn into a real test and work out where to go from there. |
Sure, although it's basically just what I linked to: #[derive(Debug, Snafu)]
enum Error {
#[doc(hidden)]
#[snafu(display("demo"))]
Demo,
} does not compile with any currently-published version of snafu 0.4.x, but did compile on 0.4.1 before 0.4.2 was published. |
I have a hunch that this is due to #107, specifically in this code. One "tricky" thing about this patch is that we have some backwards incompatible changes brewing in master. However, #136 also is ready to go, so I might need to set up a branch for 0.4 and land both this fix and that enhancement for 0.4.4. |
It would be good for you to show the error message that you get. This ensures that what we reproduce matches your behavior. |
@jgallagher do you think you can test your local code with #143? I believe that will fix it. |
Released as SNAFU 0.4.4 |
@shepmaster Sorry for the delay, can't usually respond during the day. Yep, this did fix it. The error I was getting was
Thanks for the super fast fix! |
No worries; sorry for any trouble we caused! |
Hi - big fan of snafu! I have a crate that depends on it, and it looks like I'm getting bit by a backwards-incompatible change in a patch release in snafu (amiquip/amiquip#12). Specifically, this code compiles if I download snafu 0.4.1 and change its snafu-derive dependency to
"=0.4.1"
, but breaks if it's"0.4.1"
(the published value) or"=0.4.2"
.I looked at the issues and didn't see anyone else mention this, so maybe I'm the only one that got bit by it. I'm about to publish a patch release that just removes the
#[doc(hidden)]
attribute for now, but I am curious if it's still possible to include it somehow with 0.4.3.The text was updated successfully, but these errors were encountered: