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: Values and types

Standard types

RegularExpression

On this page

A regular expression: matched whole, in linear time, with no backreferences or lookaround: [A-Z]{2}[0-9]{2}.

Software; not ordered; since Jadpo 0.1.0.

Make one

Build one from its text, RegularExpression("[A-Z]{2}[0-9]{2}"), which checks it: text that isn't one breaks format.

text.parse(raw, as: RegularExpression) reads one from its text; text that isn't one at all fails malformed, such as (a+)\1, (?<name>a)\k<name> or foo(?=bar).

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
[A-Z]{2}[0-9]{2} "[A-Z]{2}[0-9]{2}"
(?i)grey|gray "(?i)grey|gray"
\p{Lu}\w* "\\p{Lu}\\w*"

It is stored in one column named for the field, of type text. (?i)grey|gray is stored as '(?i)grey|gray'.

Shown to people

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

With locale: Locale.en_gb:

Value Shown
[A-Z]{2}[0-9]{2} [A-Z]{2}[0-9]{2}
(?i)grey|gray (?i)grey|gray
\p{Lu}\w* \p{Lu}\w*

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-regular-expression.md.Built from Jadpo main at e00e61f.