-
Notifications
You must be signed in to change notification settings - Fork 52
feat(starknet_os): integrate to_bytes and serialize_blob #4874
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
feat(starknet_os): integrate to_bytes and serialize_blob #4874
Conversation
06694cf
to
5d94ed0
Compare
d84fbbe
to
b531874
Compare
5d94ed0
to
9c18ffe
Compare
b531874
to
95496a1
Compare
Benchmark movements: |
9c18ffe
to
f752bbb
Compare
95496a1
to
cf4d3aa
Compare
Benchmark movements: |
This is considered more idiomatic, AFAIK. Suggestion: vec![0; padding]; |
f752bbb
to
e677920
Compare
cf4d3aa
to
f480f1f
Compare
e677920
to
bb48db9
Compare
f480f1f
to
2397b8f
Compare
05b48da
to
34bcf26
Compare
ed9a6a8
to
483fa50
Compare
Benchmark movements: |
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.
Reviewable status: 3 of 4 files reviewed, 1 unresolved discussion (waiting on @amosStarkware, @aner-starkware, and @nimrod-starkware)
crates/starknet_os/src/hints/hint_implementation/kzg/utils.rs
line 25 at r4 (raw file):
Previously, aner-starkware wrote…
If this is the only location, why not simply switch the order? In that case, yes, I think we should move to BigUint (though maybe it causes more overhead due to the
checked_sub
?)
Thinking again about this, I don't actually see an advantage to using biguint... the "correct" type is a "BLS field element", which we will not implement; biguint and bigint are "equally incorrect" IMO.
There is a small advantage to biguint in the sense that, if we somehow accidentally end up with a negative value, we will panic (good); I'll TAL to see how big a change this is at the top of the stack.
483fa50
to
07d1edc
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.
Reviewed 2 of 2 files at r5, 1 of 1 files at r6, all commit messages.
Reviewable status:complete! all files reviewed, all discussions resolved (waiting on @amosStarkware and @nimrod-starkware)
34bcf26
to
a87fcaf
Compare
07d1edc
to
3cc91e4
Compare
a87fcaf
to
88d04fa
Compare
3cc91e4
to
9670309
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.
Reviewed 3 of 3 files at r7, 1 of 1 files at r8, all commit messages.
Reviewable status:complete! all files reviewed, all discussions resolved (waiting on @amosStarkware and @nimrod-starkware)
88d04fa
to
eaa9752
Compare
9670309
to
1b98475
Compare
Benchmark movements: |
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.
Reviewed 2 of 2 files at r9, 1 of 1 files at r10, all commit messages.
Reviewable status:complete! all files reviewed, all discussions resolved (waiting on @amosStarkware and @nimrod-starkware)
eaa9752
to
3f66375
Compare
1b98475
to
ae26527
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.
Reviewed 1 of 1 files at r11, 1 of 1 files at r12, all commit messages.
Reviewable status:complete! all files reviewed, all discussions resolved (waiting on @amosStarkware and @nimrod-starkware)
Signed-off-by: Dori Medini <dori@starkware.co>
…ementations Signed-off-by: Dori Medini <dori@starkware.co>
ae26527
to
a282a52
Compare
Merge activity
|
No description provided.