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
Copy file name to clipboardExpand all lines: book/huff-language/macros-and-functions.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,7 +39,7 @@ by the constructor.
39
39
40
40
### Macro Arguments
41
41
42
-
Macros can accept arguments to be "called" inside the macro or passed as a reference. Macro arguments may be one of: label, opcode, literal, or a constant. Since macros are inlined at compile-time, the arguments are not evaluated at runtime and are instead inlined as well.
42
+
Macros can accept arguments, which can be used within the macro itself or passed as reference. These arguments can be labels, opcodes, literals, constants, or other macro calls. Since macros are inlined at compiletime, their arguments are also inlined and not evaluated at runtime.
43
43
44
44
#### Example
45
45
@@ -137,7 +137,7 @@ your contract, and it is essentially a trade-off of decreasing contract size
137
137
for a small extra runtime gas cost (`22 + n_inputs * 3 + n_outputs * 3` gas
138
138
per invocation, to be exact).
139
139
140
-
Functions are one of the only high-level abstractions
140
+
Functions are one of the few high-level abstractions
141
141
in Huff, so it is important to understand what the compiler adds to your code
142
142
when they are utilized. It is not always beneficial to re-use code, especially
143
143
if it is a small / inexpensive set of operations. However, for larger contracts
0 commit comments