-
Notifications
You must be signed in to change notification settings - Fork 275
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
Deprecate schnorrsig #411
Deprecate schnorrsig #411
Conversation
d03486c
to
cc30497
Compare
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.
ACK cc30497
I think the since
should be 0.22.0
rather than 0.21.3
, since 0.22.0 will be the first release with the deprecated symbols.
My bad for using the current release instead of upcoming. On the subject, is there any way to know what the next release version number is going to be? If one follows all PRs should that be obvious? Will update to 0.22.0, thanks. |
Recently we moved from using the identifier 'schnorrsig' to 'schnorr', we omitted to update the schnorr public key size constant. Deprecate `SCHNORRSIG_PUBLIC_KEY_SIZE` and add `SCHONORR_PUBLIC_KEY_SIZE`.
Recently we moved from using the identifier 'schnorrsig' to 'schnorr', we omitted to update the schnorr signature size constant. Deprecate `SCHNORRSIG_SIGNATURE_SIZE` and add `SCHONORR_SIGNATURE_SIZE`.
Recently we moved from using the identifier 'schnorrsig' to 'schnorr', we omitted to update a helper function.
Recently we moved from using the identifier 'schnorrsig' to 'schnorr', we omitted to update the tests. While we are at it use more idiomatic Rust unit test names (i.e., do not start test name with `test_` because it stutters when the name is read in output of `cargo test`).
cc30497
to
7b91f9d
Compare
Re-based, only changes were update of 'deprecate since' version. |
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.
ACK 7b91f9d
No, there is no way to tell what the next version will be :) this crate especially is something of a one-man show and we don't usually have any epics or long-term goals, it's just a question of whether we have breaking API changes in the pipeline. |
Recently we moved from using the identifier 'schnorrsig' to 'schnorr' but we missed a few places.
Change identifiers to use 'schnorr' instead of 'schnorrsig', deprecate if necessary.
Please note, does not touch
secp256k1-sys
. Use of 'schnorrsig' remains insecp256k1-sys
,