Hang Su
Hang Su
Hi, I think this trace back to the implementation in this line: https://github.com/algorand/pyteal/blob/master/pyteal/ast/bytes.py#L49, where `escapeStr` was called. The `escapeStr` was implemented in https://github.com/algorand/pyteal/blob/master/pyteal/util.py, where the function returns string **surrounded with...
yes, I need to add `set` testcases for both classes, and I need to update `abi.rst` documentation somewhat.
Just to add a related issue: some opcodes like `jsonref` has cost linear to the length of stack argument, so it cannot be handled trivially.
Another issue I am aware of deriving from https://github.com/algorand/pyteal/issues/369, how are we handling case for `Bytes("bytes-a") + Bytes("bytes-b")`? Do we expect resulting to be `Bytes("bytes-abytes-b")`, or something else? I remembered...
I believe the `abi.DynamicByteArray` can be solved by using `abi.String`. For fixed length byte array, if you want 32 byte array, we can try `abi.Address`. If we want other fixed...
oh no, feature/abi merged, you should probably remerge master branch.
Just one question to confirm: > Referencing which boxes will be used in an app call (analogous to foreign arrays) I suppose this is not quite applicable in current design...
@michaeldiamant Thanks for the description update!
`InnerTxnBuilder.MethodCall` ticket is #537, will file another PR for that
oops github is acting smart here and closed the ticket 😅