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

46 fixecdata calltoc1membershipwcp #47

Merged
merged 6 commits into from
Mar 25, 2025

Conversation

lorenzogentile404
Copy link
Contributor

No description provided.

@lorenzogentile404 lorenzogentile404 linked an issue Jan 13, 2025 that may be closed by this pull request
Copy link

cla-assistant bot commented Jan 13, 2025

CLA assistant check
All committers have signed the CLA.

Copy link

cla-assistant bot commented Jan 13, 2025

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

\utt{Third argument (high):} & \col{\cmdECDATA@var@argThreeHi} \\
\utt{Third argument (low):} & \col{\cmdECDATA@var@argThreeLo} \\
\utt{Fourth argument (high):} & \col{\cmdECDATA@var@argFourHi} \\
\utt{Fourth argument (low):} & \col{\cmdECDATA@var@argFourLo} \\
Copy link
Collaborator

Choose a reason for hiding this comment

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

I don't think we need the \col{...} stuff here, do we ? All you give it are local shorthands \locXxx which are already under \col{...}.

Copy link
Collaborator

@OlivierBBB OlivierBBB Jan 13, 2025

Choose a reason for hiding this comment

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

Also it would be nice to have more expressive names for the arguments, e.g.

\utt{x coord. hi}  & \col{\cmdECDATA@var@xHi}   \\
\utt{x coord. lo}  & \col{\cmdECDATA@var@xLo}   \\
\utt{y coord. hi}  & \col{\cmdECDATA@var@yHi}   \\
\utt{y coord. lo}  & \col{\cmdECDATA@var@yLo}   \\
\utt{LHS of (E) hi}  & \col{\cmdECDATA@var@ySquareHi}   \\
\utt{LHS of (E) lo}  & \col{\cmdECDATA@var@ySquareLo}   \\
\utt{RHS of (E) hi}  & \col{\cmdECDATA@var@xCubePlusThreeHi}   \\
\utt{RHS of (E) lo}  & \col{\cmdECDATA@var@xCubePlusThreeLo}   \vspace{2mm} \\
\multicolumn{2}{l}{\utt{Where (E) is } y^2 = x^3 + 3} \\ % as an example

with some explanation that the LHS and RHS refer to those of equation $(E) ~ \equiv ~ y^2 = x^3 + 3$ or whatever the equation is.

\utt{Third argument (high):} & \col{\cmdECDATA@var@argThreeHi} \\
\utt{Third argument (low):} & \col{\cmdECDATA@var@argThreeLo} \\
\utt{Fourth argument (high):} & \col{\cmdECDATA@var@argFourHi} \\
\utt{Fourth argument (low):} & \col{\cmdECDATA@var@argFourLo} \\
Copy link
Collaborator

Choose a reason for hiding this comment

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

same

argThreeHi = \locBYImHi ,
argThreeLo = \locBYImLo ,
argFourHi = \locBYReHi ,
argFourLo = \locBYReLo ,
Copy link
Collaborator

Choose a reason for hiding this comment

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

Same issue here: arg1 etc .. aren't expressive enough. We need better keys.

Copy link
Collaborator

@OlivierBBB OlivierBBB left a comment

Choose a reason for hiding this comment

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

LGTM. If possible I would try to convert the \callToCOneMembership method to xkeyval

\utt{x coord. hi:} & #3 \\
\utt{x coord. lo:} & #4 \\
\utt{y coord. hi:} & #5 \\
\utt{y coord. lo:} & #6 \\
Copy link
Collaborator

Choose a reason for hiding this comment

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

This should also be converted to the xkeyval package.

yImLo = \locBYImLo ,
yReHi = \locBYReHi ,
yReLo = \locBYReLo ,
}
\]

\[
Copy link
Collaborator

Choose a reason for hiding this comment

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

This space

          \]

          \[

should be removed. There are better ways to create separation if this is the goal.

@lorenzogentile404 lorenzogentile404 merged commit 0649956 into main Mar 25, 2025
1 check passed
@lorenzogentile404 lorenzogentile404 deleted the 46-fixecdata-calltoc1membershipwcp branch March 25, 2025 08:08
lorenzogentile404 added a commit that referenced this pull request Mar 25, 2025
@lorenzogentile404 lorenzogentile404 restored the 46-fixecdata-calltoc1membershipwcp branch March 25, 2025 08:41
lorenzogentile404 added a commit that referenced this pull request Mar 25, 2025
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.

fix(ecdata): callToC1MembershipWCP
2 participants