Add instructions for arbitrary sized byte arrays #231
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "arbitrary_sized_bytes"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Created by: hanssv
This PR is supported by the Æternity Crypto Foundation
Created by: radrow
Can you squeeze it below debugging instructions?
Created by: radrow
Why arg2 has to be negative?
Created by: radrow
How is it better than returning a bool? You still need to provide Arg1, so there is no point in getting it back. Also the name of the instruction is not descriptive.
Created by: radrow
Do any docs actually refer to this specifically chosen -1?
Created by: hanssv
It doesn't have to be negative, it can be negative. The alternative would be a three argument function, I thought this was more compact.
Created by: hanssv
You have something of type
bytes()
and want something of typebytes(n)
then a boolean wont help you? TheArg1
has typebytes(Arg2)
- perhaps the explanation can be improved...Created by: hanssv
Yes, sure!
Created by: hanssv
Not yet - but it should go into
protocol
at some point.Created by: hanssv
At the FATE level the types will not differ
Created by: radrow
Ah, so it's casting! Makes sense
Created by: radrow
I misread, makes sense now
Created by: radrow
Review: Approved
approved this merge request
Merged by: ghallak at 2023-05-27 14:13:20 UTC