-
Notifications
You must be signed in to change notification settings - Fork 340
async std unstable feature compiles wasm crates on non-wasm arch #823
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
Comments
Since |
we pull it in if we don’t have smol as runtime activated. unfortunately the flags are not perfect so it currently doesn‘t quite work out. we might be able to improve on this with the latest smol refactors |
Gentle +1, it would be great to not have to chew through all those crates if we are not targeting wasm. (especially on my platform(OpenBSD) where |
should be fixed on master |
Versions:
My platform:
x86_64-apple-darwin
Async-std version: 1.6.2
rust version: both
rustc 1.44.1 (c7087fe00 2020-06-17)
andrustc 1.46.0-nightly (a8cf39911 2020-06-21)
Issue:
This line
async-std/Cargo.toml
Line 81 in 17ab958
unstable
feature is enabled regardless of the target_arch. This means that crates that use theunstable
feature such as http-rs/http-types and http-rs/tide have to compileweb-sys
andjs-sys
.These are the changes to
cargo tree --features unstable
when commenting out that line, which shouldn't be activated onx86_64-apple-darwin
. I don't assume that the fix is actually to comment this line out. Is this a cargo bug?The text was updated successfully, but these errors were encountered: