-
Notifications
You must be signed in to change notification settings - Fork 61
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
compilation fix #67
compilation fix #67
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is just lint warnings, right? @stevenroose is in the process of releasing right now so I'm not sure this will go in. Thanks for coming back to do the fix!
Actually compilation error, CI failed on master with new rustc version: |
fixing: error: the item `ToString` is imported redundantly --> src/lib.rs:48:26 error: the item `Vec` is imported redundantly --> src/lib.rs:48:44 error: could not compile `bip39` (lib) due to 2 previous errors
73a108e
to
6ce654b
Compare
It is not a compiler problem as I stated in previous comment.
Error message I see is:
All checks in Line 57 in b100bf3
As the result the crate cannot be used as a dep w/o @tcharding @stevenroose do you think we can still have a fix in 2.1.0? |
This is all caused by a recent rustc upgrade, here is an issue where we are discussing it in
EDIT: huh? I don't get any errors on master right now? @michalkucharczyk are you seeing errors on |
Yes. Just run this on master (
This happens for both:
and:
|
Bizzare, I am not getting errors with $ cargo +nightly --version
cargo 1.79.0-nightly (a59aba136 2024-03-28)
$ cargo +nightly build --release --no-default-features --features=alloc --lib Nor with $ cargo --version
cargo 1.77.1 (e52e36006 2024-03-26)
$ cargo build --release --no-default-features --features=alloc --lib No clue what is going on. |
dq: did you try The other way to reproduce is creating a simple crate with bip39 as dep. Following the steps listed below generates the same error for me:
|
Wow, seems I am the wombat :) I had commented this line in Line 57 in b100bf3
But you should be able to reproduce problem with the commands I provided in my previous comment. |
fix proposed in: #69 |
Oh boy, took me so long to work out that the |
fixing following error (introduced in #57):