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

secp256k1: Tighten max magnitudes in comments. #3442

Merged
merged 1 commit into from
Sep 9, 2024

Conversation

davecgh
Copy link
Member

@davecgh davecgh commented Sep 8, 2024

The FieldVal type was originally an internal only type and the comments regarding the magnitudes were written from that perspective along with the the understanding that the stated maximum magnitudes referred to the max results during normalization.

However, now that the type is external, it was pointed out that the magnitude comments are misleading since it is not explicitly made clear anywhere that they refer to what ultimately happens during normalization as opposed to the specific methods in question.

In order to prevent potential confusion, this updates all of the comments regarding max magnitudes to be framed in terms of an external perspective and the specific method they are commenting on such that it ultimately ensures normalization is guaranteed not to exceed that actual internal maximum magnitude.

@davecgh davecgh added the documentation Issues and/or pull requests related to documentation. label Sep 8, 2024
@davecgh davecgh added this to the 2.1.0 milestone Sep 8, 2024
The FieldVal type was originally an internal only type and the comments
regarding the magnitudes were written from that perspective along with
the the understanding that the stated maximum magnitudes referred to the
max results during normalization.

However, now that the type is external, it was pointed out that the
magnitude comments are misleading since it is not explicitly made clear
anywhere that they refer to what ultimately happens during normalization
as opposed to the specific methods in question.

In order to prevent potential confusion, this updates all of the
comments regarding max magnitudes to be framed in terms of an external
perspective and the specific method they are commenting on such that it
ultimately ensures normalization is guaranteed not to exceed that actual
internal maximum magnitude.
@davecgh davecgh merged commit 7b6403e into decred:master Sep 9, 2024
2 checks passed
@davecgh davecgh deleted the secp256k1_clarify_magnitudes branch September 9, 2024 17:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Issues and/or pull requests related to documentation.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants