Unison identifiers come in two flavors:
- Regular identifiersstart with an alphabetic unicode character, emoji (which is any unicode character between 1F400 and 1FAFF inclusive), or underscore (''_''), followed by any number of alphanumeric characters, emoji, or the characters
set!are valid regular identifiers.
- Operatorsconsist entirely of the characters
>>=are valid operators.
Thegeneral reference for identifiersdescribesunqualifiedidentifiers. An identifier can also be qualified. A qualified identifier consists of a qualifier or namespace, followed by a
.,followed by either a regular identifier or an operator. The qualifier is one or more regular identifiers separated by
Foo.Bar.bazis a qualified identifier where
Foo.Baris the qualifier.
Absolutely qualified identifiers
Note that absolutely qualified identifiers are much less prevalent with the advent of Unison projects. They refer to a term from the root of the entire codebase, not the root of a particular project, so their usage is limited to legacy support of a pre-project era.
Namespace-qualified identifiersare relative to a “current” namespace, which the programmer can set (and defaults to the root of the current project). To ignore the current namespace, an identifier can have anabsolute qualifier.An absolutely qualified name begins with a
..For example, the name
.base.Listalways refers to the name
.base.List,regardless of the current project or namespace, whereas the name
base.Listwill refer to
lib.base.Listif the current namespace contains the
baselibrary in its
Any identifier, including a namespace-qualified one, can appearhash-qualified.A hash-qualified identifier has the form
xis an identifier and
#his ahash literal.The hash disambiguates names that may refer to more than one thing.
The following names are reserved by Unison and cannot be used as identifiers: