-
Notifications
You must be signed in to change notification settings - Fork 302
Unified container parsing enforces typecode order. #474
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
Conversation
d5dbda3 to
f17ab99
Compare
f17ab99 to
89cd7ec
Compare
Codecov Report
@@ Coverage Diff @@
## master #474 +/- ##
==========================================
+ Coverage 50.30% 50.35% +0.04%
==========================================
Files 88 88
Lines 7941 7963 +22
==========================================
+ Hits 3995 4010 +15
- Misses 3946 3953 +7
Continue to review full report at Codecov.
|
89cd7ec to
6bd8225
Compare
|
UA test vectors need to be updated for the tests here to pass. |
6bd8225 to
33880c0
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.
Should this be cloning typecodes before mutating it? It doesn't seem common for arb_* functions to mutate their arguments, and I'm not sure whether there are any special requirements to make shrinking work.
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.
Since this takes ownership, there's no need to clone it, right? The shrinking question is interesting, but I think the answer to that is that this should really take a set of typecodes, not a vec since the uniqueness property needs to hold anyway.
daira
left a comment
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.
utACK with suggestions.
55b7fb4 to
5682ffe
Compare
|
One style issue that I note this PR raises: we now have two canonical orderings for typecodes (preference order and encoding order) and as such it feels like the |
a23e3f8 to
a9c9fbf
Compare
Co-authored-by: Daira Hopwood <daira@jacaranda.org>
Co-authored-by: Daira Hopwood <daira@jacaranda.org>
There are two canonical orderings for sealed items: preference order and encoding order. Removing the `Ord` instances means that a user can't accidentally choose the wrong ordering; these orderings are replaced by explicit `preference_order` and `encoding_order` comparison functions.
c31ff8e to
e3c67ff
Compare
str4d
left a comment
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.
utACK. I verified that the updated test vectors here match the ones generated by zcash/zcash-test-vectors@61894e7.
No description provided.