aboutsummaryrefslogtreecommitdiff
path: root/language_description.md
diff options
context:
space:
mode:
authorRunxi Yu <me@runxiyu.org>2024-12-10 05:11:01 +0800
committerRunxi Yu <me@runxiyu.org>2024-12-11 00:42:17 +0800
commitf8955de50bb021ea1a7a2b61e745259f46f82953 (patch)
tree69f9a580b61a35c3e675c8542e36cb034da4a0f1 /language_description.md
parentSome changes, and some examples to start with for error propagation (diff)
downloade2-spec-f8955de50bb021ea1a7a2b61e745259f46f82953.tar.gz
e2-spec-f8955de50bb021ea1a7a2b61e745259f46f82953.tar.zst
e2-spec-f8955de50bb021ea1a7a2b61e745259f46f82953.zip
s/err/error/g
Diffstat (limited to 'language_description.md')
-rw-r--r--language_description.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/language_description.md b/language_description.md
index fd54e50..4c175bf 100644
--- a/language_description.md
+++ b/language_description.md
@@ -37,7 +37,7 @@ function could not be called (for example, if the stack is full). For example,
`malloc` for allocating dynamic memory could be structured like this:
```e2
-func malloc(size_t s) (void*, err) {
+func malloc(size_t s) (void*, error) {
/* What malloc is supposed to do */
return ptr, NIL;
} onfail {
@@ -56,7 +56,7 @@ error, so it might be natural to set their error return value to something like
`ESTACK`:
```e2
-func f() (err) {
+func f() (error) {
return NIL;
} onfail {
return ESTACK;