From 5bb4d2e4a5dc9a83461b2c689a3d01cd92db8f86 Mon Sep 17 00:00:00 2001 From: Dummi26 Date: Wed, 19 Apr 2023 16:16:34 +0200 Subject: [PATCH] readme claimed &statement was valid, but it isn't. now it correctly states that &varname must be used to get a reference. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index e95b983..81a7b30 100755 --- a/README.md +++ b/README.md @@ -391,7 +391,7 @@ Mers has the following builtin types: - thread + a special type returned by the thread builtin. It is similar to JavaScript promises and can be awaited to get the value once it has finished computing. Reading the thread example is probably the best way to see how this works. - reference - + a mutable reference to a value. `&type` for the type and `&statement` for a reference value (usually `&varname`). + + a mutable reference to a value. `&type` for the type and `&varname` for a reference value. - enum + wraps any other value with a certain identifier. + the type is written as `enum(type)`: many builtins use `Err(String)` to report errors.