-
Notifications
You must be signed in to change notification settings - Fork 10
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
Big Refactor According to Updated Spec #44
base: main
Are you sure you want to change the base?
Conversation
Reference C implementation: cryptape/omnilock#3 Changes: - add lazy reader support - API changed - add testing - add documents. make it ready for publishing - fix according to updated spec - add logs
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.
No obvious problems.
* Add testcases, about cobuild_normal_entry * Add some cycles checks for normal and successful cases.
Just a quick glance at this PR: I could get the underlying change, but at this stage, I wasn't so sure about the API change, where we moved completely into a callback based design, instead of Rust iterators. I fear this might be far too big a change. Even if we switch from current design to a lazy loader based design, I feel like we can still keep much of the current APIs, yes there might be one or two data structure change but that will pretty much be it. I wonder if we need to completely overhaul this, especially when the updated API, looks quite messy to me. |
I do recommend that we split it into 3 smaller PRs:
|
Reference C implementation: cryptape/omnilock#3
Changes:
Note to reviewers:
i
,j
,ie
,oe
are from spec