Async-std: Please don't pull in wasm dependencies (via gloo-timers) on non-wasm platforms
async-std with the unstable feature enabled pulls in various wasm-specific dependencies via the gloo-timers dependency of futures-timer, even on non-wasm platforms. This adds quite a few dependencies, and shows up when building tide.
joshtriplett
All 5 comments
@joshtriplett agreed; we should fix that.
yoshuawuyts
on 28 Aug 2020
When I looked into this I was confused why this happens because in Cargo.toml it looks like the features are separated per target. I think it is related to https://github.com/rust-lang/cargo/issues/1197 .
e00E
on 28 Aug 2020
Possible fix at https://github.com/async-rs/async-std/pull/864 doesn't rely on target-specific features and switches to a wasm feature, which would be semver-major for wasm users.
As far as I can tell, this issue also ends up interfering with the alloc feature
jbr
on 28 Aug 2020
See also this older duplicate issue: https://github.com/async-rs/async-std/issues/823
Fishrock123
on 2 Sep 2020
fixed on master
dignifiedquire
on 16 Sep 2020
Related issues
yoshuawuyts
路
5Comments
Licenser
路
8Comments
yoshuawuyts
路
6Comments
oblique
路
5Comments
yoshuawuyts
路
6Comments
Most helpful comment
When I looked into this I was confused why this happens because in Cargo.toml it looks like the features are separated per target. I think it is related to https://github.com/rust-lang/cargo/issues/1197 .