Syntax reference

Elixir syntax was designed to have a straightforward conversion to an abstract syntax tree (AST). This means the Elixir syntax is mostly uniform with a handful of "syntax sugar" constructs to reduce the noise in common Elixir idioms.

This document covers all of Elixir syntax constructs as a reference and then discuss their exact AST representation.

Reserved words

These are the reserved words in the Elixir language. They are detailed throughout this guide but summed up here for convenience:

  • true, false, nil - used as atoms
  • when, and, or, not, in - used as operators
  • fn - used for anonymous function definitions
  • do, end, catch, rescue, after, else - used in do/end blocks

Data types


Integers (1234) and floats (123.4) in Elixir are represented as a sequence of digits that may be separated by underscore for readability purposes, such as 1_000_000. Integers never contain a dot (.) in their representation. Floats contain a dot and at least one other digit after the dot. Floats also support the scientific notation, such as 123.4e10 or 123.4E10.


Unquoted atoms start with a colon (:) which must be immediately followed by an underscore or a Unicode letter. The atom may continue using a sequence of Unicode letters, numbers, underscores, and @. Atoms may end in ! or ?. See Unicode Syntax for a formal specification. Valid unquoted atoms are: :ok, :ISO8601, and :integer?.

If the colon is immediately followed by a pair of double- or single-quotes surrounding the atom name, the atom is considered quoted. In contrast with an unquoted atom, this one can be made of any Unicode character (not only letters), such as :'🌢 Elixir', :"++olá++", and :"123".

Quoted and unquoted atoms with the same name are considered equivalent, so :atom, :"atom", and :'atom' represent the same atom. The only catch is that the compiler will warn when quotes are used in atoms that do not need to be quoted.

All operators in Elixir are also valid atoms. Valid examples are :foo, :FOO, :foo_42, :foo@bar, and :++. Invalid examples are :@foo (@ is not allowed at start), :123 (numbers are not allowed at start), and :(*) (not a valid operator).

true, false, and nil are reserved words that are represented by the atoms :true, :false and :nil respectively.


Single-line strings in Elixir are written between double-quotes, such as "foo". Any double-quote inside the string must be escaped with \. Strings support Unicode characters and are stored as UTF-8 encoded binaries.

Multi-line strings in Elixir are written with three double-quotes, and can have unescaped quotes within them. The resulting string will end with a newline. The indentation of the last """ is used to strip indentation from the inner string. For example:

iex> test = """
...>     this
...>     is
...>     a
...>     test
...> """
"    this\n    is\n    a\n    test\n"
iex> test = """
...>     This
...>     Is
...>     A
...>     Test
...>     """

Strings are always represented as themselves in the AST.


Charlists in Elixir are written in single-quotes, such as 'foo'. Any single-quote inside the string must be escaped with \. Charlists are made of non-negative integers, where each integer represents a Unicode code point.

Multi-line charlists are written with three single-quotes ('''), the same way multi-line strings are.

Charlists are always represented as themselves in the AST.

For more in-depth information, please read the "Charlists" section in the List module.

Lists, tuples and binaries

Data structures such as lists, tuples, and binaries are marked respectively by the delimiters [...], {...}, and <<...>>. Each element is separated by comma. A trailing comma is also allowed, such as in [1, 2, 3,].

Maps and keyword lists

Maps use the %{...} notation and each key-value is given by pairs marked with =>, such as %{"hello" => 1, 2 => "world"}.

Both keyword lists (list of two-element tuples where the first element is atom) and maps with atom keys support a keyword notation where the colon character : is moved to the end of the atom. %{hello: "world"} is equivalent to %{:hello => "world"} and [foo: :bar] is equivalent to [{:foo, :bar}]. This notation is a syntax sugar that emits the same AST representation. It will be explained in later sections.


Structs built on the map syntax by passing the struct name between % and {. For example, %User{...}.



Variables in Elixir must start with an underscore or a Unicode letter that is not in uppercase or titlecase. The variable may continue using a sequence of Unicode letters, numbers, and underscores. Variables may end in ? or !. See Unicode Syntax for a formal specification.

Elixir's naming conventions recommend variables to be in snake_case format.

Non-qualified calls (local calls)

Non-qualified calls, such as add(1, 2), must start with an underscore or a Unicode letter that is not in uppercase or titlecase. The call may continue using a sequence of Unicode letters, numbers, and underscore. Calls may end in ? or !. See Unicode Syntax for a formal specification.

Parentheses for non-qualified calls are optional, except for zero-arity calls, which would then be ambiguous with variables. If parentheses are used, they must immediately follow the function name without spaces. For example, add (1, 2) is a syntax error, since (1, 2) is treated as an invalid block which is attempted to be given as a single argument to add.

Elixir's naming conventions recommend calls to be in snake_case format.


As many programming languages, Elixir also support operators as non-qualified calls with their precedence and associativity rules. Constructs such as =, when, & and @ are simply treated as operators. See the Operators page for a full reference.

Qualified calls (remote calls)

Qualified calls, such as Math.add(1, 2), must start with an underscore or a Unicode letter that is not in uppercase or titlecase. The call may continue using a sequence of Unicode letters, numbers, and underscores. Calls may end in ? or !. See Unicode Syntax for a formal specification.

Elixir's naming conventions recommend calls to be in snake_case format.

For qualified calls, Elixir also allows the function name to be written between double- or single-quotes, allowing calls such as Math."++add++"(1, 2). Operators can be used as qualified calls without a need for quote, such as Kernel.+(1, 2).

Parentheses for qualified calls are optional. If parentheses are used, they must immediately follow the function name without spaces.


Aliases are constructs that expand to atoms at compile-time. The alias String expands to the atom :"Elixir.String". Aliases must start with an ASCII uppercase character which may be followed by any ASCII letter, number, or underscore. Non-ASCII characters are not supported in aliases.

Elixir's naming conventions recommend aliases to be in CamelCase format.


Blocks are multiple Elixir expressions separated by newlines or semi-colons. A new block may be created at any moment by using parentheses.

Left to right arrow

The left to right arrow (->) is used to establish a relationship between left and right, commonly referred as clauses. The left side may have zero, one, or more arguments; the right side is zero, one, or more expressions separated by new line. The -> may appear one or more times between one of the following terminators: do/end, fn/end or (/). When -> is used, only other clauses are allowed between those terminators. Mixing clauses and regular expressions is invalid syntax.

It is seen on case and cond constructs between do/end:

case 1 do
  2 -> 3
  4 -> 5

cond do
  true -> false

Seen in typespecs between (/):

(integer(), boolean() -> integer())

It is also used between fn/end for building anonymous functions:

  x, y -> x + y


Sigils start with ~ and are followed by a letter and one of the following pairs:

  • ( and )
  • { and }
  • [ and ]
  • < and >
  • " and "
  • ' and '
  • | and |
  • / and /

After closing the pair, zero or more ASCII letters can be given as a modifier. Sigils are expressed as non-qualified calls prefixed with sigil_ where the first argument is the sigil contents as a string and the second argument is a list of integers as modifiers:

If the sigil letter is in uppercase, no interpolation is allowed in the sigil, otherwise its contents may be dynamic. Compare the results of the sigils below for more information:


Sigils are useful to encode text with their own escaping rules, such as regular expressions, datetimes, and others.

The Elixir AST

Elixir syntax was designed to have a straightforward conversion to an abstract syntax tree (AST). Elixir's AST is a regular Elixir data structure composed of the following elements:

  • atoms - such as :foo
  • integers - such as 42
  • floats - such as 13.1
  • strings - such as "hello"
  • lists - such as [1, 2, 3]
  • tuples with two elements - such as {"hello", :world}
  • tuples with three elements, representing calls or variables, as explained next

The building block of Elixir's AST is a call, such as:

sum(1, 2, 3)

which is represented as a tuple with three elements:

{:sum, meta, [1, 2, 3]}

the first element is an atom (or another tuple), the second element is a list of two-element tuples with metadata (such as line numbers) and the third is a list of arguments.

We can retrieve the AST for any Elixir expression by calling quote:

quote do
#=> {:sum, [], []}

Variables are also represented using a tuple with three elements and a combination of lists and atoms, for example:

quote do
#=> {:sum, [], Elixir}

You can see that variables are also represented with a tuple, except the third element is an atom expressing the variable context.

Over the course of this section, we will explore many Elixir syntax constructs alongside their AST representations.


Operators are treated as non-qualified calls:

quote do
  1 + 2
#=> {:+, [], [1, 2]}

Note that . is also an operator. Remote calls use the dot in the AST with two arguments, where the second argument is always an atom:

quote do, 2, 3)
#=> {{:., [], [{:foo, [], Elixir}, :bar]}, [], [1, 2, 3]}

Calling anonymous functions uses the dot in the AST with a single argument, mirroring the fact the function name is "missing" from right side of the dot:

quote do
  foo.(1, 2, 3)
#=> {{:., [], [{:foo, [], Elixir}]}, [], [1, 2, 3]}


Aliases are represented by an __aliases__ call with each segment separated by dot as an argument:

quote do
#=> {:__aliases__, [], [:Foo, :Bar, :Baz]}

quote do
#=> {:__aliases__, [], [{:__MODULE__, [], Elixir}, :Bar, :Baz]}

All arguments, except the first, are guaranteed to be atoms.

Data structures

Remember lists are literals, so they are represented as themselves in the AST:

quote do
  [1, 2, 3]
#=> [1, 2, 3]

Tuples have their own representation, except for two-element tuples, which are represented as themselves:

quote do
  {1, 2}
#=> {1, 2}

quote do
  {1, 2, 3}
#=> {:{}, [], [1, 2, 3]}

Binaries have a representation similar to tuples, except they are tagged with :<<>> instead of :{}:

quote do
  <<1, 2, 3>>
#=> {:<<>>, [], [1, 2, 3]}

The same applies to maps where each pair is treated as a list of tuples with two elements:

quote do
  %{1 => 2, 3 => 4}
#=> {:%{}, [], [{1, 2}, {3, 4}]}


Blocks are represented as a __block__ call with each line as a separate argument:

quote do
#=> {:__block__, [], [1, 2, 3]}

quote do 1; 2; 3; end
#=> {:__block__, [], [1, 2, 3]}

Left to right arrow

The left to right arrow (->) is represented similar to operators except that they are always part of a list, its left side represents a list of arguments and the right side is an expression.

For example, in case and cond:

quote do
  case 1 do
    2 -> 3
    4 -> 5
#=> {:case, [], [1, [do: [{:->, [], [[2], 3]}, {:->, [], [[4], 5]}]]]}

quote do
  cond do
    true -> false
#=> {:cond, [], [[do: [{:->, [], [[true], false]}]]]}

Between (/):

quote do
  (1, 2 -> 3
   4, 5 -> 6)
#=> [{:->, [], [[1, 2], 3]}, {:->, [], [[4, 5], 6]}]

Between fn/end:

quote do
    1, 2 -> 3
    4, 5 -> 6
#=> {:fn, [], [{:->, [], [[1, 2], 3]}, {:->, [], [[4, 5], 6]}]}

Syntactic sugar

All of the constructs above are part of Elixir's syntax and have their own representation as part of the Elixir AST. This section will discuss the remaining constructs that "desugar" to one of the constructs explored above. In other words, the constructs below can be represented in more than one way in your Elixir code and retain AST equivalence.

Integers in other bases and Unicode code points

Elixir allows integers to contain _ to separate digits and provides conveniences to represent integers in other bases:

#=> 1000000

#=> 43981 (Hexadecimal base)

#=> 342391 (Octal base)

#=> 170 (Binary base)

#=> 233 (Unicode code point)

Those constructs exist only at the syntax level. All of the examples above are represented as their underlying integers in the AST.

Access syntax

The access syntax is represented as a call to Access.get/2:

quote do
#=> {{:., [], [Access, :get]}, [], [{:opts, [], Elixir}, {:arg, [], Elixir}]}

Optional parentheses

Elixir provides optional parentheses for non-qualified and qualified calls.

quote do
  sum 1, 2, 3
#=> {:sum, [], [1, 2, 3]}

The above is treated the same as sum(1, 2, 3) by the parser.

The same applies to qualified calls such as, 2, 3), which is equivalent to 1, 2, 3. There are, however, some situations where parentheses are required:

  • when calling anonymous functions, such as f.(1, 2);

  • for non-qualified calls with no arguments, such as sum(). Removing the parentheses for sum causes it to be represented as the variable sum;

  • for dynamic qualified calls with no arguments. data.key means accessing a field named key in the map given by data., with parens, means calling a function named fun in the module mod;

In practice, developers prefer to add parentheses to most of their calls. They are skipped mainly in Elixir's control-flow constructs, such as defmodule, if, case, etc, and in certain DSLs.


Keywords in Elixir are a list of tuples of two elements where the first element is an atom. Using the base constructs, they would be represented as:

[{:foo, 1}, {:bar, 2}]

However Elixir introduces a syntax sugar where the keywords above may be written as follows:

[foo: 1, bar: 2]

Atoms with foreign characters, such as whitespace, must be wrapped in quotes. This rule applies to keywords as well:

[{:"foo bar", 1}, {:"bar baz", 2}] == ["foo bar": 1, "bar baz": 2]

Remember that, because lists and two-element tuples are quoted literals, by definition keywords are also literals (in fact, the only reason tuples with two elements are quoted literals is to support keywords as literals).

Keywords as last arguments

Elixir also supports a syntax where if the last argument of a call is a keyword list then the square brackets can be skipped. This means that the following:

if(condition, do: this, else: that)

is the same as

if(condition, [do: this, else: that])

which in turn is the same as

if(condition, [{:do, this}, {:else, that}])

do/end blocks

The last syntax convenience are do/end blocks. do/end blocks are equivalent to keywords as the last argument of a function call where the block contents are wrapped in parentheses. For example:

if true do

is the same as:

if(true, do: (this), else: (that))

which we have explored in the previous section.

Parentheses are important to support multiple expressions. This:

if true do

is the same as:

if(true, do: (

Inside do/end blocks you may introduce other keywords, such as else used in the if above. The supported keywords between do/end are static and are:

  • after
  • catch
  • else
  • rescue

You can see them being used in constructs such as receive, try, and others.


This document provides a reference to Elixir syntax, exploring its constructs and their AST equivalents.

We have also discussed a handful of syntax conveniences provided by Elixir. Those conveniences are what allow us to write

defmodule Math do
  def add(a, b) do
    a + b

instead of

defmodule(Math, [
  {:do, def(add(a, b), [{:do, a + b}])}

The mapping between code and data (the underlying AST) is what allows Elixir to implement defmodule, def, if, and others in Elixir itself. Elixir makes the constructs available for building the language accessible to developers who want to extend the language to new domains.