-
Notifications
You must be signed in to change notification settings - Fork 13.4k
std
depends on cfg-if
1.0.0 and 0.1.10
#103365
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
@rustbot label T-libs |
Note that this bloat is only exposed to users of -Zbuild-std so it doesn't matter much. I'd take a patch removing it from
|
not exactly true, it's shipped in the normal distribution:
Though it is pretty minor.
Locally I was able to update it from 0.1.14 -> 0.1.16, which depends on cfg-if 1.0.0. Will this break in ways I don't understand? |
Good point.
That's probably be fine. I think the issue is with getrandom 0.2 rather than the 0.1.x series -- whichever one requires wasm_bindgen for the wasm impl and compile_errors when it fails to resolve an impl (since std cannot depend on wasm-bindgen). Feel free to |
Cool! I put it up for discussion: #103367 |
Update test's cfg-if dependency to 1.0 This change was mistakenly left out of rust-lang#103367 Finishes rust-lang#103365
Remove std's transitive dependency on cfg-if 0.1 After rust-lang/rust#101946 this completes the move to cfg-if 1.0 by: * Updating getrandom 0.1.14->0.1.16 * Updating panic_abort's and unwind's dep to cfg-if 1.0 Fixes rust-lang/rust#103365
#101861 added
cfg-if
v1.0.0 as astd
dependency.std
still depends oncfg-if
v0.1.10:Depending on only one version would be nice. While it's a small library, it's still unnecessary bloat.
The text was updated successfully, but these errors were encountered: