-
Notifications
You must be signed in to change notification settings - Fork 148
The dependencies of the bigint
feature on rand
and rustc_serialize
should be optional.
#151
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
See rust-lang/rust#30713. |
Oops, here's the real issue: If you build with the |
rand
feature completely disables BigInt
bigint
feature on rand
and rustc_serialize
should be optional.
Sure, making these fully optional would be welcome. It used to be mandatory for So these two would be dropped from |
Just to be clear, you would accept this?:
|
My pull request #154 fixes this.
Optional dependencies are handled like features, so I didn't need to do this.
I did this.
I made it conditional on the "rustc_serialize" feature.
I did this, but I also had to enable the
I did this. |
#154 is merged. |
Thanks for the quick turnaround. Is there going to be a release to crates.io soon that will include this change? Thanks! |
I suppose we should. I don't like publishing a release with dirty CI, but this change in particular will help others get around the |
num 0.1.30 is now published. |
My builds are failing on Nightly because I depend on
num
and therand
crate fails to build on Nightly. My crate only depends onrand
because it depends onBigInt
. I tried to build without therand
dependency but that madeBigInt
unavailable.Instead all of
BigInt
being dependent on therand
feature, only the random-related parts ofBigint
should depend on therand
feature. And, in particular, when buildingnum
without therand
feature, the rest ofBigInt
should work.The text was updated successfully, but these errors were encountered: