Gauntlet Documentation
  • 🏠Welcome
  • 🏅Getting Started
    • 🧠Introduction To Gauntlet
  • ‼️Read before Proceeding
  • ⬇️Installation
  • 👨‍💻VSCode Extension
  • 📚Basics
    • 💨Running Gauntlet
    • 📄File Setup & Hello World
  • 🔠Scope Variables
  • 🖼️Constants
  • 🧩Functions
  • ↔️If Statements
  • 🔑Ternary Operator
  • 💠Switch-Case
  • 📩Select-Case
  • ➰Loops
  • 📁Structs
  • 🧱Interfaces
  • 🪪Aliases
  • 📎Methods
  • 🦙Lambdas
  • 🕸️Miscellaneous
  • ⚡Advanced Features
    • 🔀When-Cases
    • 🚥Tagged Unions
    • 🎚️Pattern Matching
    • 🚰Pipes
    • ⁉️Try-Statements
    • 🎭Force-Statements
    • 🌯Wrapper Types
  • 🔼Version Release Notes
    • v0.2.0-alpha
Powered by GitBook
On this page
  • New Features
  • Tagged Unions
  • Pattern Matching
  • Modifications
  • New Syntax
  • New Pipe Operator
  • Discord and GitHub
Export as PDF
  1. Version Release Notes

v0.2.0-alpha

PreviousWrapper Types

Last updated 23 hours ago

New Features

Tagged Unions

Hit the button below to read the documentation regarding tagged unions

Pattern Matching

Hit the button below to read the documentation regarding pattern matching

Modifications

New Syntax

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

// 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:

// 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.

🔼
🚥Tagged Unions
🎚️Pattern Matching