-
-
Notifications
You must be signed in to change notification settings - Fork 265
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
proc-macro derive produced unparseable tokens as of nightly-2019-11-25 #429
Comments
In case it's of interest, I think this is the grammar in question:
|
Minimal repro: mod grammar {
#[derive(::pest_derive::Parser)]
#[grammar_inline = "
union = { SOI }
"]
struct Parser;
}
I'm currently attempting to reduce the issue to report upstream. Thanks for reporting this! (To avoid things like this in the future, we should potentially always emit raw identifiers. This makes sure that any identifier will always work without odd problems, though it might require raw identifier syntax to use. It is allowed to use unnecessary raw identifiers, and is equivalent to the non-raw identifier.) |
Glad it was easy to spot! |
I got lucky noticing that you were using a pseudo-keyword and intuiting that was the problem 😛 Even more minimized: pub enum Rule {
union,
} This works on Reported upstream as rust-lang/rust#66943 |
rust-lang/rust#66943 was closed two days ago, and I was able to build using nightly (latest) just now without issue. Thanks for facilitating the upstream fix! |
I was looking into arabidopsis/typescript-definitions#4 and the pest usage (Parser derive) there works on
nightly-2019-11-24
, but breaks onnightly-2019-11-25
. I'm not familiar with pest, and so I'm unsure if this is an issue specific to the grammar being fed into the proc macro, or something else.I note that the pest test suite builds and runs fine on both sides of the toolchain boundary, so again, I'm very unsure of where the issue actually lies.
Looking for some direction/advice if you've got it for me. Thanks!
The text was updated successfully, but these errors were encountered: