-
Notifications
You must be signed in to change notification settings - Fork 20
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
error: proc-macro derive produced unparseable tokens #4
Comments
|
Looking closer, it was suggested the issue reported to pest was caused by ambigious module names (which is not the case here as far as I can tell). Just to rule it out, I fussed with the use statements and the path in the derive attribute itself to no avail. I'm not exactly sure what the issue is. |
I still don't have any real solutions, but what I see in master right now. I can get the crate to build...
diff --git a/typescript-definitions-derive/src/attrs.rs b/typescript-definitions-derive/src/attrs.rs
index 83a6867..43b3546 100644
--- a/typescript-definitions-derive/src/attrs.rs
+++ b/typescript-definitions-derive/src/attrs.rs
@@ -12,7 +12,6 @@ use quote::quote;
use proc_macro2::TokenStream;
use syn::{Attribute, Ident, Lit, Meta, /* MetaList,*/ MetaNameValue, NestedMeta};
-#[derive(Debug)]
pub struct Attrs {
pub comments: Vec<String>,
pub guard: bool, The removal of the derived |
Short-term fix: rename the I'm looking into what changed and will report a bug to upstream rust for this changed behavior. |
Thanks @CAD97. I'll keep my toolchain pinned for now and track the upstream bug on rust for progress. Probably doesn't make much sense to patch around this immediately if holding the toolchain back is enough for now. |
Looks like the "unparsable tokens" issue should be fixed as of 2 days ago since rust-lang/rust#66943 has been merged through. We should be able to track nightly freely once more. |
This is a cool project. Thanks for releasing it! I am getting an error in typescript.rs:40.
I can trigger this with a very simple main.rs:
The text was updated successfully, but these errors were encountered: