urbit/developers.urbit.org
1
1
Fork 0
mirror of https://github.com/urbit/developers.urbit.org.git synced 2024-08-16 17:20:35 +03:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #329 from leowini/main

Browse Source 
nock: fix typo
This commit is contained in:
tinnus-napbus 2023-04-11 21:32:02 +12:00 committed by GitHub
commit ec5a903365
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
content/reference/nock/explanation.md
View File

@ -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