-
Notifications
You must be signed in to change notification settings - Fork 15
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
Range checks for types #210
Conversation
@rooooooooob is this ready for review? |
I was just going to add more tests but I noticed I found some cases are not actually handled right. I'll try and see if I can get this fixed and ready today. |
now tests for both preserve-encodings and not with all 3 of those as well as bounds that go across both
@gostkin it's ready now. While making the test cases I noticed there were actually some annoying to solve cases not covered/implemented but now we should have everything covered for nint/uint/int with ranges above/below for preserve-encodings and without (+ the length ones for arrays/maps/text/bytes). |
Specifically tests for support for #121 for plain groups. For multi arrays covered by #120 For single ones covered by #210 We are keeping #121 open for now as the case for single non-plain-groups e.g. `[uint]` is not covered. We've yet to see this used anywhere in Cardano so it's low priority to fix.
Specifically tests for support for #121 for plain groups. For multi arrays covered by #120 For single ones covered by #210 We are keeping #121 open for now as the case for single non-plain-groups e.g. `[uint]` is not covered. We've yet to see this used anywhere in Cardano so it's low priority to fix.
Range tests for all types (except floats). Ints, text, bytes, maps, arrays.
Covers preserve-encodings=true and =false.
Includes test cases for both.
also fixes some clippy warnings in generated code