aboutsummaryrefslogtreecommitdiff
path: root/examples
diff options
context:
space:
mode:
authorKimplul <kimi.h.kuparinen@gmail.com>2026-03-13 14:07:29 +0200
committerKimplul <kimi.h.kuparinen@gmail.com>2026-03-13 14:09:53 +0200
commited7da0d9e31e8dd6847e2e603f0d1943330cf4d0 (patch)
tree16e4785bd92f43a37bed6b0028b0f239faa00d51 /examples
parent25b8db28cf87708808744b97774c2a8427e129e2 (diff)
downloadfwd-ed7da0d9e31e8dd6847e2e603f0d1943330cf4d0.tar.gz
fwd-ed7da0d9e31e8dd6847e2e603f0d1943330cf4d0.zip
add initial reference invalidation
+ Makes vec example actually memory safe, which is cool + Specify owner > sub relationships with ">" in closure parameter lists, uses the same group idea as closure calls + Relies on users implementing functions in a consistent manner, since you can kind of do whatever with pointers. Presumably there would be a stdlib of vec/map/set etc. which applications could then use and by proxy be memory safe. Although some more checks wouldn't hurt, I suppose? + Not sure I like having reference invalidation be 'just a move', seems to work alright but the semantics of it are a bit muddy.
Diffstat (limited to 'examples')
-rw-r--r--examples/vec.fwd2
1 files changed, 1 insertions, 1 deletions
diff --git a/examples/vec.fwd b/examples/vec.fwd
index 6950c2a..75c5b2e 100644
--- a/examples/vec.fwd
+++ b/examples/vec.fwd
@@ -75,7 +75,7 @@ append_vec(vec v, i64 e, (vec) ok)
ok(v);
}
-at_vec(vec v, u64 i, (vec, &i64) ok)
+at_vec(vec v, u64 i, (vec > &i64) ok)
{
v => [n => n, s => s, buf => buf];
guard(i < n) => {