Skip to content
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 BASEPOINT_ORDER from pub API consts #581

Merged
merged 4 commits into from
Sep 18, 2023

Conversation

pinkforest
Copy link
Contributor

Deprecates BASEPOINT_ORDER from pub API constants

Redirect internally to avoid deprecation errors

@@ -94,6 +78,9 @@ pub const BASEPOINT_ORDER: Scalar = Scalar {
],
};

#[allow(deprecated)]
pub(crate) const BASEPOINT_ORDER_PRIVATE: Scalar = BASEPOINT_ORDER;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe reverse this relationship so BASEPOINT_ORDER_PRIVATE defines the constant and BASEPOINT_ORDER points to BASEPOINT_ORDER_PRIVATE?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ah ofcourse, thanks 💜

Copy link
Contributor

@tarcieri tarcieri left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems like there are a lot of unrelated changes in this PR now?

@pinkforest
Copy link
Contributor Author

Fixed - Forgot to rebase

pinkforest and others added 2 commits September 13, 2023 04:39
Co-authored-by: Tony Arcieri <bascule@gmail.com>
@rozbb rozbb merged commit 533b53a into dalek-cryptography:main Sep 18, 2023
22 checks passed
@marshallpierce
Copy link

marshallpierce commented Oct 10, 2023

I have a use for this constant (I need to exponentiate a scalar by order - 2) -- would it be objectionable to un-deprecate this? Otherwise I'll need to construct my own copy of a constant, which would be a shame.

Edit: I found another way, never mind!

@trevor-crypto
Copy link

@marshallpierce what was the solution? 🤔 Just making your own constant?

@marshallpierce
Copy link

It turned out I was doing curve operations in a needlessly complex way. I don't have the details in front of me, but tl;dr I found a way to do what I needed to do using other public parts of the API.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants