From aec19e55ca32f68536a550f100d3f058b8a93c02 Mon Sep 17 00:00:00 2001 From: Kimplul Date: Sat, 4 Jan 2025 01:25:31 +0200 Subject: initial move checking + Missing implementations for most things, but it already highlights an oversight in my initial plan, namely that currently, a function might call multiple of its closures, meaning that a closure wouldn't be allowed to move a value. I'm debating whether to check that only one closure from a parameter list is called at a time or if I should do what Hylo does and add in some kind of 'subscript' that's like a function but has slightly different rules? --- src/debug.c | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'src/debug.c') diff --git a/src/debug.c b/src/debug.c index cd0b8eb..f72fe9b 100644 --- a/src/debug.c +++ b/src/debug.c @@ -144,6 +144,12 @@ void type_mismatch(struct scope *scope, struct ast *node, free((void *)rs); } +void move_error(struct ast *new_use, struct ast *prev_use) +{ + semantic_error(new_use->scope, new_use, "using moved value"); + semantic_info(prev_use->scope, prev_use, "previously moved here"); +} + static void _type_str(FILE *f, struct type *t); static void _type_list_str(FILE *f, struct type *types) -- cgit v1.2.3