-
Notifications
You must be signed in to change notification settings - Fork 182
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
Support custom implementations of Trace LDE #207
Conversation
ee5baa5
to
01d9338
Compare
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.
Looks great! Thank you! This is basically how I thought about this as well. I left a few comments inline. Most of them are pretty minor, except for the last comment which is about potentially adding a new()
constructor to TraceLde
and using it instead of Prover::new_trace_lde()
.
Regarding the tests: I think it would be great to have unit tests on DefaultTraceLde
- so, I'd prefer if the removed tests were moved there. Looking at them, they may actually be a bit simpler now as it doesn't seem like we need to instantiate Air
to test these behavior on DefaultTraceLde
.
2373566
to
24a1399
Compare
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.
Looks good! Thank you! I left a couple small comments inline. We can probably merge and address these in a separate commit.
Oh - one other thing: we should add an entry to the changelog file for this. |
This PR addresses #180. It's not quite ready for merge, but I'd like to get feedback on the approach
TraceLde
struct to a traitTraceLde