-
Notifications
You must be signed in to change notification settings - Fork 160
Fix use of Result in macro output #462
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
Conversation
KodrAus
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for working on this @james7132! I think we just need to update the serde_core version to one that's actually published, but otherwise this looks good to me.
KodrAus
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just spotted one more nitpick, then this should be good to go!
|
I had a look at those build failures and fixed this up in #467. If you'd like to scope this PR back to just the |
|
Currently on vacation, will do so sometime next week. |
|
@KodrAus done! |
KodrAus
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @james7132!
Serde recently split out the trait definitions from the top level serde crate. This crate does not rely on the derive macro, so it should be effective to depend on serde_core instead of serde. This doesn't impact the compilation times of bitflags itself, but allows it to parallelize withDone in #467.serde-deriveand potentially other crates likeserde-jsonthat also do not rely on the derive macro, unblocking other crates reliant on bitflags to do so as well.This PR fully qualifies the path of the use of Result in the generated macro code.