on master help sign in
rune: describe =* as macro, not alias (#826)

Given the "evaluate when used" nature of =*, it's more accurately described as a macro than an alias.

commit0230efc1e20d4b1728584412c328f31b56055613 authorFang <git@fang.io> dateTue 21 Apr 2020, 21:59 (7 years ago) parent65c4896
1 file changed+4−4
reference/hoon-expressions/rune/tis.md+4−4
reference/hoon-expressions/rune/tis.md+4−4
@@ -423,11 +423,11 @@ Regular: **running**.
423423
424424### =* "tistar"
425425
426−`[%tstr p=term q=hoon r=hoon]`: define an alias.
426+`[%tstr p=term q=hoon r=hoon]`: define a macro.
427427
428428##### Produces
429429
430−`r`, compiled with a subject in which `p` is aliased to `q`.
430+`r`, compiled with a subject in which `p` is a macro for `q`.
431431
432432##### Syntax
433433
@@ -435,7 +435,7 @@ Regular: **3-fixed**.
435435
436436##### Discussion
437437
438−The difference between aliasing and pinning is that pinning changes the subject, but for aliasing the subject noun stays the same. The aliased expression, `q`, is recorded in the type information of `p`. `q` is calculated every time you use the `p` alias.
438+The difference between macroing and pinning is that pinning changes the subject, but for macroing the subject noun stays the same. The macro'd expression, `q`, is recorded in the type information of `p`. `q` is calculated every time you use the `p` macro.
439439
440440##### Examples
441441
@@ -487,4 +487,4 @@ the type of `p`.
487487
488488> =?(a =(1 2) 22 a)
48948912
490−```
490+```