# --, == · Terminators

The `--` and `==` are used as terminators: `--` for core expressions, and `==` for terminating a 'running' or 'jogging' series of Hoon expressions.

## -- "hephep" <a href="#hephep" id="hephep"></a>

#### Syntax

The `--` rune is used to indicate the end of a core expression.

#### Discussion

The `|%`, `|_`, and `|^` runes are used to create cores that can have arbitrarily many arms. When you have defined all the desired arms in a core expression (using the `++`, `+$`, and `+*` runes), use `--` to terminate the expression.

#### Examples

```
> =num |%
         ++  two  2
         ++  add-two  |=(a=@ (add 2 a))
         ++  double  |=(a=@ (mul 2 a))
       --

> two.num
2

> (add-two.num 12)
14

> (double.num 12)
24
```

***

## == "tistis" <a href="#tistis" id="tistis"></a>

#### Syntax

The `==` rune is used to indicate the end of a 'jogging' or 'running' series of Hoon expressions (runes that take a variable number of arguments).

#### Discussion

Certain runes are used to create expressions that may include arbitrarily many subexpressions. Such expressions are terminated with the `==` rune. For example, the `:*` and `:~` runes are used to create a cell of any length. (The latter is just like the former except that it adds a null value at the end of the cell.) For another example, the `%=` rune used used to make arbitrarily many changes to a given wing value.

#### Examples

```
> :*  2
      3
      4
      5
      6
  ==
[2 3 4 5 6]

> :~  2
      3
      4
      5
      6
  ==
[2 3 4 5 6 ~]

> =values [a=12 b=14 c=16 d=18 e=20]

> %=  values
    a  13
    b  15
    c  17
    d  19
    e  21
  ==
[a=13 b=15 c=17 d=19 e=21]
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.urbit.org/hoon/rune/terminators.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
