Sigils

Sigils provide custom parsing for complex literals. They start with ~ followed by a tag and a delimiter.

// Regex
pattern = ~r/\w+@\w+\.\w+/

// URL
endpoint = ~u(https://api.example.com)

// Date
birthday = ~d(1990-12-31)

// I18n key and message templates
welcomeKey = ~k"app.welcome"
welcomeMsg = ~m"Hello, {name:Text}!"

Domains define these sigils to validate and construct types at compile time.

Structured sigils

Some domains parse sigils as AIVI expressions rather than raw text. For v1.0, the Collections domain defines:

// Map literal (entries use =>, spread with ...)
users = ~map{
  "id-1" => { name: "Alice" }
  "id-2" => { name: "Bob" }
}

// Set literal (spread with ...)
tags = ~set[...baseTags, "hot", "new"]

The exact meaning of a sigil is domain-defined; see Collections for ~map and ~set.