You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 20, 2024. It is now read-only.
We would like a way for the stack comments to be automatically generated.
by stack comments we are referring to inline comments to the right representing the current known state of the stack:
0x20 // [length]
0x0 // [offset, length]
One way we discussed was creating a new huff-fmt command that would got through Huff files and add stack annotations. Maybe someday it would be nice to have a editor extension that can add the comments.
As part of this work, we need to figure out how to assign labels or aliases for items on the stack.
For incoming/outgoing stack items, it has been suggest that maybe we define the aliases along with the takes(x) returns(x) at the macro(fn) definition level, so perhaps takes(2, [owner, spender]) returns (1, [returnValue]).
Alternatively, aliases could be defined in a comment at the beginning of the macro so:
We would like a way for the stack comments to be automatically generated.
by stack comments we are referring to inline comments to the right representing the current known state of the stack:
One way we discussed was creating a new
huff-fmt
command that would got through Huff files and add stack annotations. Maybe someday it would be nice to have a editor extension that can add the comments.As part of this work, we need to figure out how to assign labels or aliases for items on the stack.
For incoming/outgoing stack items, it has been suggest that maybe we define the aliases along with the
takes(x) returns(x)
at the macro(fn) definition level, so perhapstakes(2, [owner, spender]) returns (1, [returnValue])
.Alternatively, aliases could be defined in a comment at the beginning of the macro so:
It would also be great to be able to alias intermediate stack items so one idea is:
would elicit:
For values with left padded zero's, one idea is to exclude the zeros so:
would elicit:
It has also been suggested that the stack generating logic would work with constants so:
would elicit:
The text was updated successfully, but these errors were encountered: