> For the complete documentation index, see [llms.txt](https://gauntletlang.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gauntletlang.gitbook.io/docs/version-release-notes/v0.2.0-alpha.md).

# v0.2.0-alpha

## New Features

### Tagged Unions

Hit the button below to read the documentation regarding tagged unions

{% content-ref url="/pages/yxlTr6g6rqXvlS8NZpuR" %}
[Tagged Unions](/docs/advanced-features/tagged-unions.md)
{% endcontent-ref %}

### Pattern Matching

Hit the button below to read the documentation regarding pattern matching

{% content-ref url="/pages/PZk8MEPQ0PpwEBMstcpM" %}
[Pattern Matching](/docs/advanced-features/pattern-matching.md)
{% endcontent-ref %}

## Modifications

### New Syntax

In the previous version of the language, the type would always come before the name. For example:

```fsharp
// Old Syntax - <type> <name>
fun getGreeting(String fullName)
```

in this new version, this aspect been reversed: the type will now always come *after* the name, seperated by a colon:

```fsharp
// New Syntax - <name>: <type>
fun getGreeting(fullName: String)
```

### New Pipe Operator

The pipe operator has been changed from `=>` to `|>`.

## Discord and GitHub

Experince issues, or want to get involved? Please join the Discord server and/or create an issue on the GitHub page. Links can be found [here](/docs/read-before-proceeding.md#useful-links).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://gauntletlang.gitbook.io/docs/version-release-notes/v0.2.0-alpha.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.