high-level, safe, and simple programming language
Go to file
2023-06-06 13:51:33 +02:00
.github/workflows Update rust.yml 2023-04-30 22:31:43 +02:00
build_scripts added build script for musl libc 2023-05-27 17:56:10 +02:00
docs fix typo 2023-06-04 22:15:09 +02:00
examples . 2023-06-04 22:23:10 +02:00
mers changed VType internals 2023-06-06 13:51:33 +02:00
mers_libs changed VData system again, renamed src/script to src/lang and added src/c.mers, which is an example something that currently does not work properly due to the VData implementation (and serves as a reminder to fix the issue) 2023-05-14 00:11:36 +02:00
site update readme, docs, site, and version to 0.2.0. 2023-06-04 21:59:38 +02:00
.gitignore changed gitignore 2023-04-30 21:38:37 +02:00
external.css update colors 2023-06-04 22:06:21 +02:00
index.html update readme, docs, site, and version to 0.2.0. 2023-06-04 21:59:38 +02:00
README.md update readme, docs, site, and version to 0.2.0. 2023-06-04 21:59:38 +02:00

mers build status

Mers is an experimental programming language inspired by high-level and scripting languages, but with error handling inspired by rust.

Why mers?

mers has...

  • the type-safety of statically typed languages
    • mers will not crash unless you exit() with a nonzero exit code or write flawed assumptions using the builtin .assume*() functions (Rust's unwrap or expect)
  • the flexibility of dynamically typed languages
    • x := if condition() { "my string" } else { 12 } // <- this is valid
  • "correctness" (this is subjective and I'll be happy to discuss some of these decisions with people)
    • there is no null / nil
    • all references are explicit: if you pass a list by value, the original list will never be modified in any way.
    • errors are normal values! (no special treatment)
  • a flexible type system to easily represent these errors and any complex structure including recursive types:
    • nothing: [] (an empty tuple)
    • a string: string
    • two strings: [string string] (a tuple)
    • many strings: [string ...] (a list)
    • Either a string or nothing (Rust's Option<String>): string/[]
    • Either an int or an error: (Rust's Result<isize, String>): int/string (better: int/Err(string))
  • compile-time execution through (explicit) macro syntax: !(mers {<code>}) or !(mers "file")

How mers?

Mers is written in rust. If you have cargo, use the build script in build_scripts/ to produce the executable.

Now, create a new text file (or choose one from the examples) and run it: mers <file>.

Docs

syntax cheat sheet

intro

builtins

statements