mirror of
https://github.com/urbit/developers.urbit.org.git
synced 2024-08-16 17:20:35 +03:00
typo
This commit is contained in:
parent
b0101d0dc6
commit
e5c0145472
@ -29,8 +29,8 @@ For instance, it's common to represent strings (or even whole
|
||||
text files) as atoms, arranging them LSB first - so "foo" becomes
|
||||
`0x6f6f66`. How do we know to print this as "foo", not `0x6f6f66`?
|
||||
We need external information - such as a Hoon type. Similarly,
|
||||
other common atomic types - signed integers, floating point, etc
|
||||
- are all straightforward to map into atoms.
|
||||
other common atomic types - signed integers, floating point, etc -
|
||||
are all straightforward to map into atoms.
|
||||
|
||||
It's also important to note that, unlike Lisp, Nock cannot create
|
||||
cyclical data structures. It is normal and common for nouns in a
|
||||
|
Loading…
Reference in New Issue
Block a user