You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I noticed recently while working on winit that it no longer builds in the stdweb configuration due to this crate. Building instant directly yields (rustc 1.38.0 (625451e37 2019-09-23)):
PS D:\code\instant> cargo build --target wasm32-unknown-unknown --features stdweb
Compiling instant v0.1.2 (D:\code\instant)
error[E0433]: failed to resolve: use of undeclared type or module `wasm_bindgen`
--> src\wasm.rs:92:13
|
92 | let v = js! { return performance.now(); };
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ use of undeclared type or module `wasm_bindgen`
|
= note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
error[E0433]: failed to resolve: use of undeclared type or module `WasmDescribe`
--> src\wasm.rs:92:13
|
92 | let v = js! { return performance.now(); };
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ use of undeclared type or module `WasmDescribe`
|
= note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
error[E0425]: cannot find function `inform` in this scope
--> src\wasm.rs:92:13
|
92 | let v = js! { return performance.now(); };
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ not found in this scope
|
= note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
error[E0425]: cannot find value `FUNCTION` in this scope
--> src\wasm.rs:92:13
|
92 | let v = js! { return performance.now(); };
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ not found in this scope
|
= note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
error: aborting due to 4 previous errors
Some errors have detailed explanations: E0425, E0433.
For more information about an error, try `rustc --explain E0425`.
error: Could not compile `instant`.
To learn more, run the command again with --verbose.
This was working in the past (sorry! I don't know exactly when!) and I noticed this in the last week or so. I'm pretty confident the stdweb and wasm-bindgen versions don't matter here, as I've tried older versions with the same results.
Adding an explicit dependency in instant's Cargo.toml to wasm-bindgen seems to solve the problem, but I'm mostly confused that (as far as I know) nothing changed to cause this break...?
Edit: I just realized I may have upgraded rust itself in between this working and not. Looking through the changelog, maybe rust-lang/cargo#6860 could cause a change here? But 1.36.0 was released in July and the last successful CI build for instant ran when 1.1.2 released earlier this month. 😕
The text was updated successfully, but these errors were encountered:
Hi, I noticed recently while working on
winit
that it no longer builds in thestdweb
configuration due to this crate. Buildinginstant
directly yields (rustc 1.38.0 (625451e37 2019-09-23)
):This was working in the past (sorry! I don't know exactly when!) and I noticed this in the last week or so. I'm pretty confident the
stdweb
andwasm-bindgen
versions don't matter here, as I've tried older versions with the same results.Adding an explicit dependency in
instant
'sCargo.toml
towasm-bindgen
seems to solve the problem, but I'm mostly confused that (as far as I know) nothing changed to cause this break...?Edit: I just realized I may have upgraded rust itself in between this working and not. Looking through the changelog, maybe rust-lang/cargo#6860 could cause a change here? But 1.36.0 was released in July and the last successful CI build for
instant
ran when 1.1.2 released earlier this month. 😕The text was updated successfully, but these errors were encountered: