mark/mers
1
0
Fork 0
mirror of https://github.com/Dummi26/mers.git synced 2025-03-10 14:13:52 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity

include a.f(b) syntax

Browse Source
This commit is contained in:
Mark 2023-10-27 19:24:54 +02:00
parent 078b83dfa5
commit b914b11af6
1 changed files with 11 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
README.md
View File

@ -27,9 +27,11 @@ Mers is built around a type-system where a value could be one of multiple types.
``` ```
x := if condition { 12 } else { "something went wrong" } x := if condition { 12 } else { "something went wrong" }
``` ```
In mers, the compiler tracks all the types in your program, In mers, the compiler tracks all the types in your program,
and it will catch every possible crash before the program even runs: and it will catch every possible crash before the program even runs:
If we tried to use `x` as an int, the compiler would complain since it might be a string, so this **does not compile**: If we tried to use `x` as an int, the compiler would complain since it might be a string, so this **does not compile**:
``` ```
list := (1, 2, if true 3 else "not an int") list := (1, 2, if true 3 else "not an int")
list.sum.println list.sum.println
@ -37,6 +39,7 @@ list.sum.println
Type-safety for functions is different from what you might expect. Type-safety for functions is different from what you might expect.
You don't need to tell mers what type your function's argument has - you just use it however you want as if mers was a dynamically typed language: You don't need to tell mers what type your function's argument has - you just use it however you want as if mers was a dynamically typed language:
``` ```
sum_doubled := iter -> { sum_doubled := iter -> {
one := iter.sum one := iter.sum
@ -44,13 +47,14 @@ sum_doubled := iter -> {
} }
(1, 2, 3).sum_doubled.println (1, 2, 3).sum_doubled.println
``` ```
We could try to use the function improperly by passing a string instead of an int: We could try to use the function improperly by passing a string instead of an int:
``` ```
(1, 2, "3").sum_doubled.println (1, 2, "3").sum_doubled.println
``` ```
But mers will catch this and show an error, because the call to `sum` inside of `sum_doubled` would fail.
(note: type-checks aren't implemented for all functions yet - some are just `todo!()`s, so mers will crash while checking your program. you may need to use `--check no` to get around this and deal with runtime panics for now) But mers will catch this and show an error, because the call to `sum` inside of `sum_doubled` would fail.
### Error Handling ### Error Handling
@ -65,17 +69,14 @@ So, if we want to print the programs stdout, we could try
stdout.println stdout.println
``` ```
But if we encountered a `RunCommandError`, mers couldn't assign the value to `(s, stdout, stderr)`, so this doesn't compile. But if we encountered a `RunCommandError`, mers wouldn't be able to assign the value to `(s, stdout, stderr)`, so this doesn't compile.
Instead, we need to handle the error case, using the `try` function: Instead, we need to handle the error case, using the `try` function:
``` ```
( ("ls", ("/")).run_command.try((
("ls", ("/")).run_command,
(
(s, stdout, stderr) -> stdout.println, (s, stdout, stderr) -> stdout.println,
error -> error.println, error -> error.println,
) ))
).try
``` ```
## docs ## docs