-
-
Notifications
You must be signed in to change notification settings - Fork 811
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
Issues with the new serde_derive
system
#567
Comments
Thanks for reporting these! The first one is fixed in rust-lang/rust#36782 and will be in tomorrow's nightly. The second one I filed as rust-lang/cargo#3132. |
I confirmed that The doc issue is in progress at rust-lang/rust#36847. |
Thanks very much by the way for the quick progress made on these two issues. |
The rustdoc fix just merged. I will leave this ticket open until I can confirm that it works. |
I confirmed that |
When using that plugin, there are two errors:
Both of these are easily solvable by following the compiler's instructions. But I suppose my question is, why are these needed in the first place and should it be documented so that new users don't get tripped up?
Additionally if I run
cargo doc
then cargo tries to document theserde_derive
crate and complains because it contains items with#[rustc_macro_derive]
.I realise it is super early days for
serde_derive
but I thought I'd just point out these issues as from some quick searching I can't see any acknowledgement of them.The text was updated successfully, but these errors were encountered: