-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
js-sys
fails to build with nightlies on and after 2020-05-25
#2158
Labels
Comments
This was referenced May 26, 2020
I opened an issue on |
@alexcrichton the issue was fixed by dtolnay/syn#834; with syn 1.0.27 I no longer get the error (locally). I think if the CI jobs on #2161 run again things should Just Work. |
Awesome, thanks so much for your help here @rrbutani! |
(Nice sleuthing by the way) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the Bug
js-sys
fails to build withrustc
nightlies on and afternightly-2020-05-25
.Steps to Reproduce
js-sys
with a toolchain newer thannightly-2020-05-24
:rustup install nightly-2020-05-25
cargo +nightly-2020-05-25 build -p js-sys
Expected Behavior
The build succeeds!
Actual Behavior
The build does not succeed.
Additional Context
Running cargo-bisect-rustc pins it down to this rollup and from there it's fairly straightforward to pick out rust-lang/rust#72388.
Here's the output from
cargo-bisect-rustc
if it helps:bisected with cargo-bisect-rustc v0.5.1
searched nightlies: from nightly-2020-05-24 to nightly-2020-05-26
regressed nightly: nightly-2020-05-25
searched commits: from rust-lang/rust@8970e8b to rust-lang/rust@46e85b4
regressed commit: rust-lang/rust@7726070
Host triple: x86_64-unknown-linux-gnu
Reproduce with:
The cause of this error, as best as I can tell, is that
$name
in this macro goes from being passed to#[wasm_bindgen]
as asyn::Type::Path
to being passed in as asyn::Group
containing thesyn::Type::Path
that the macro wants (as in the span that$name
is in isn't discarded).wasm_bindgen
's parser doesn't know to handle this (here and here) and so we get the errors above.There's already an issue open in rust-lang/rust for this: rust-lang/rust#72545. For that specific issue the crate in question was using
proc-macro-hack
but as shown the same change can also break proc macros that don't use it.The text was updated successfully, but these errors were encountered: