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

Fix mlkzg::EvaluationArgument fields #207

Merged
merged 1 commit into from
Dec 20, 2023
Merged

Conversation

adr1anh
Copy link
Contributor

@adr1anh adr1anh commented Dec 20, 2023

No description provided.

Copy link
Contributor

@huitseeker huitseeker left a comment

Choose a reason for hiding this comment

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

I completely misunderstood your comment, thanks for fixing 🤦

evals_r_squared: Vec<Vec<E::Fr>>,
comms: Vec<E::G1Affine>,
w: Vec<E::G1Affine>,
evals: Vec<Vec<E::Fr>>,
Copy link
Contributor

Choose a reason for hiding this comment

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

if evals.len() is known to be 3, an array may make more sense.

@adr1anh adr1anh marked this pull request as ready for review December 20, 2023 20:16
@adr1anh
Copy link
Contributor Author

adr1anh commented Dec 20, 2023

Given that @storojs72 is working on it at the moment, I just wanted to get this quick fix in so the code is clearer. I agree that we should probably use an array instead though.

@adr1anh adr1anh requested a review from huitseeker December 20, 2023 20:18
@huitseeker huitseeker added this pull request to the merge queue Dec 20, 2023
Merged via the queue into lurk-lang:dev with commit cca3e63 Dec 20, 2023
4 of 8 checks passed
@adr1anh adr1anh deleted the fix-evals branch January 2, 2024 16:23
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.

2 participants