-
Notifications
You must be signed in to change notification settings - Fork 737
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
CCQ/EVM: Testing library for building responses #3768
CCQ/EVM: Testing library for building responses #3768
Conversation
8eed896
to
8894390
Compare
a1ab016
to
f0ca59f
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.
What do you think about all the buildXXXBytes
methods also returning the length of the bytes being returned?
There are a lot of lengths passed around that presumably a user has to manually fetch themselves with BYTES.length
.
If we did this you can disregard my inline comment
@djb15, I changed the functions to derive the length from the bytes passed in, which I think eliminates the need to make the functions also return the length? Please let me know if you disagree. |
ee0b650
to
feae3f5
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.
Changes look good to me! Byte array lengths aren't being checked but I think we'll be hard pressed to be using 4GB byte arrays
No description provided.