on master help sign in
blog/why-hoon: can the footnote
441686bMatilde Park
content/blog/why-hoon.md+1−3
@@ -116,10 +116,8 @@ Hoon and Nock have several unusual properties:
116 there are no cycles in Nock's memory model. Pointer equality is not
116 there are no cycles in Nock's memory model. Pointer equality is not
117 exposed to the programmer. In practical Nock implementations, all
117 exposed to the programmer. In practical Nock implementations, all
118 data structures are what are elsewhere called "functional" or
118 data structures are what are elsewhere called "functional" or
119− "persistent" data structures, meaning they're immutable<sup>*</sup> and share
119+ "persistent" data structures, meaning they're immutable and share
120 structure wherever possible.
120 structure wherever possible.
121− <br/><small>*with the exception of "unifying
122− equality", which some runtimes provide as an optimization</small><br/>
123
121
124- **Homoiconic**. Code and data are represented the same way and can be
122- **Homoiconic**. Code and data are represented the same way and can be
125 converted to each other. Lisp dialects are also homoiconic, but Hoon
123 converted to each other. Lisp dialects are also homoiconic, but Hoon