Jadpo is experimental and not ready for production. These docs follow the compiler's main branch as of 1 Nov 2026. What's built ยท Install 0.2.0
jadpo
Reference: Standard library

Standard types

Emoji

On this page

One emoji (UTS #51), fully qualified, as Unicode's list writes it: a red heart is U+2764 U+FE0F.

Web and network; not ordered; since Jadpo 0.1.0.

Make one

Build one from its text, Emoji("๐Ÿ˜€"), which checks it: text that isn't one breaks format.

text.parse(raw, as: Emoji) reads one from its text; text that isn't one at all fails malformed, such as โค, ๐Ÿฝ or ๐Ÿ˜€๐Ÿ˜€.

Text, JSON and storage

text.from writes its canonical text, the one form text.parse reads back. JSON sends its canonical text as a string.

Text JSON
๐Ÿ˜€ "๐Ÿ˜€"
๐Ÿ‘๐Ÿฝ "๐Ÿ‘๐Ÿฝ"
๐Ÿ‘จโ€๐Ÿ‘ฉโ€๐Ÿ‘ง "๐Ÿ‘จโ€๐Ÿ‘ฉโ€๐Ÿ‘ง"
๐Ÿ‡ฌ๐Ÿ‡ง "๐Ÿ‡ฌ๐Ÿ‡ง"
โค๏ธ "โค๏ธ"

It is stored in one column named for the field, of type text. ๐Ÿ‘จโ€๐Ÿ‘ฉโ€๐Ÿ‘ง is stored as '๐Ÿ‘จโ€๐Ÿ‘ฉโ€๐Ÿ‘ง'.

Shown to people

text.format(value, locale:) shows it to people in their locale.

With locale: Locale.en_gb:

Value Shown
๐Ÿ˜€ ๐Ÿ˜€
๐Ÿ‘๐Ÿฝ ๐Ÿ‘๐Ÿฝ
๐Ÿ‘จโ€๐Ÿ‘ฉโ€๐Ÿ‘ง ๐Ÿ‘จโ€๐Ÿ‘ฉโ€๐Ÿ‘ง
๐Ÿ‡ฌ๐Ÿ‡ง ๐Ÿ‡ฌ๐Ÿ‡ง
โค๏ธ โค๏ธ

Operations

It has the contract's own operations: text.parse, text.from, text.format, json.read, json.write and ==. It isn't ordered, so < and sorting don't take it. Every standard type meets one contract says how they work.

Markdown for agents: /docs/types/type-emoji.md.Built from Jadpo main at e00e61f.