-
Notifications
You must be signed in to change notification settings - Fork 1
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
chore: repo cleaning, remove unused code paths #84
Conversation
…its directory. Fixes circom-lsp path issues.
work started, a lot of circom to clean up and de-duplicate. There are several tests that fail to compile at the moment, most notably the aes-gcm circuit appears to be broken. @0xJepsen maybe we could fix this when we pair. repro: there were some other broken tests I was able to fix or remove for irrelevance, and I commented out a few particularly slow, irrelevant tests. also, i added circom lib to our circuits area, which previously blocked my lsp from building. lmk if you'd prefer i just keep that gitignored. |
7daf3e8
to
2ac5fd3
Compare
2ac5fd3
to
c8ca209
Compare
Why duplicate the circomlib code instead of importing? |
what do you mean @devloper |
This pull requests copies all of the circuits from circomlib into the repository. With circom you can specify an include flag, such as |
removed circomlib, added to my gitignore until further discussion |
756a245
to
93a349e
Compare
@devloper What do you think about removing the |
@@ -65,3 +64,36 @@ describe("Cipher", () => { | |||
); | |||
}); | |||
}); | |||
|
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.
what's the deal here?
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.
💩
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.
fair
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.
seems mostly renaming and code deletion, good stuff. I'm not sure what the inputs stuff was used for, pending tracy's approval
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.
i thought you used mulx in your implementation?
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.
I do but not the one this tested / i moved it into the mul_test
|
Closes #82.
Closes #81
Note: All tests pass right now except the aes-gcm one because the new components need to get plugged in correctly. @devloper I assume you grabbed those?