17 releases (5 breaking)

new 0.8.2 Apr 16, 2024
0.7.3 Mar 22, 2024

#345 in Programming languages

Download history 9/week @ 2024-01-09 45/week @ 2024-01-16 11/week @ 2024-01-30 373/week @ 2024-02-13 139/week @ 2024-02-20 153/week @ 2024-02-27 26/week @ 2024-03-05 44/week @ 2024-03-12 328/week @ 2024-03-19 20/week @ 2024-03-26 87/week @ 2024-04-02

483 downloads per month
Used in mers


7.5K SLoC


The library behind mers.

With this, you can parse, compile, check and run mers code. You can also add your own functions and types which can then be used from mers, if you really want to.

Running mers

There are four steps to running mers code. The examples show you how to actually implement them, this readme only explains what they do any why.

1. Parsing

This first step converts the source code, a string, to a parsed mers statement.

In this step, syntax errors and unknown variables are caught.

2. Compiling

This converts a parsed mers statement to a compiled one. It almost never produces an error.

3. Checking

This step is optional. If you parse and compile your source code, you can (try to) run it. However, mers assumes that all mers code you run is actually valid, so if you don't check your codes validity, mers will probably panic while running your code.

This step performs all the type-checking and determines the output type of your code, if it is valid.

For example, the following code is valid and has the return type Int/Float:

my_condition := true

if my_condition {
} else {

4. Running

This step assumes that the code it is running is actually valid, so it never returns an error. As long as check didn't return an error in Step 3, it is safe to assume that this will return the value produced by the code. We can also assume that the return value has a type which is included in that determined by check. If check returned an error, this will likely panic.


~52K SLoC