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

Update text-overview.md

Browse Source
This commit is contained in:
Sigilante 2022-11-14 18:02:08 -06:00 committed by GitHub
parent 56d613c125
commit 7455caa0b0
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/blog/text-overview.md
View File

@ -16,7 +16,7 @@ image = "https://media.urbit.org/site/posts/essays/blog-text-bottles.png"
[Text strings](https://en.wikipedia.org/wiki/String_%28computer_science%29%) are sequences of characters. At one level, the file containing code is itself a string—at a more fine-grained level, we take strings to mean either byte sequences obtained from literals (like `'Hello Mars'`) or from external APIs. This blog post will expand on [existing docs](https://developers.urbit.org/guides/additional/strings) to explain what is going on with text in various corners of Hoon.
Setting aside [literal syntax](TODO), Urbit distinguishes quite a few text representation types:
Setting aside [literal syntax](https://developers.urbit.org/blog/literals), Urbit distinguishes quite a few text representation types:
1. `cord`s (`@t`, [LSB](https://en.wikipedia.org/wiki/Bit_numbering#Least_significant_byte))
2. `knot`s (`@ta`)