Update batched token draft 5 #63
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
armfazh
approved these changes
Jul 7, 2025
|
after merging, let's do a release as this new version changes the package names. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updating the repository to fully implement the next draft of batched tokens.
It allows individual use of Type5 instead of solely within amortized version.
It also allows for amortized Type1.
This required a restructure of the repository to use private and amortized instead of type1 and type5.
Another PR will updated "batched" to "generic" to be consistent with the draft.
The new implementation work against previously generated test vectors, and against the Rust test vectors
@raphaelrobert if you want the test vector generated by Go implementation, they are here