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

Rebase of #201 #224

Merged
merged 16 commits into from
Jan 23, 2023
Merged

Rebase of #201 #224

merged 16 commits into from
Jan 23, 2023

Conversation

weissjeffm
Copy link
Contributor

The master branch diverged significantly since #201 was started, and merging/rebasing was basically impossible. This is a rebase of some of the earlier commits and then manual replaying of the rest of the changes. Doing manual edits is rather error prone but hopefully I got everything.

Also update some store-related functions that can only return
StoreError, to return that instead of a more generic LurkError.
The only place this is used is in proofs, so the name seems more
fitting.
Errors during reduce will be dealt with later, with an explicit notion
of a provable vs non-provable error.
Split into two functions, one which considers provable errors a rust
Result::Err just like any other error. Then a higher level function
that examines any error and if it's Provable, return the proper
Control object. Pass any other errors up.

TODO: the Control object has a Ptr in the first field, even in the
case of errors. Need to preserve that.
@weissjeffm weissjeffm mentioned this pull request Jan 20, 2023
2 tasks
src/eval.rs Outdated
}
pub fn output_vector(&self, store: &Store<F>) -> Result<Vec<F>, store::Error> {
self.output.to_vector(store)
}
Copy link
Collaborator

Choose a reason for hiding this comment

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

I think these got re-added accidentally.

Copy link
Collaborator

@porcuquine porcuquine left a comment

Choose a reason for hiding this comment

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

🎉

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