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/analyze.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/analyze.c') diff --git a/src/analyze.c b/src/analyze.c index 37b2e65..077e7d8 100644 --- a/src/analyze.c +++ b/src/analyze.c @@ -418,7 +418,7 @@ static int analyze(struct state *state, struct scope *scope, struct ast *node) case AST_CONST_STR: ret = analyze_str (state, scope, node); break; default: - internal_error("missing ast analysis"); + internal_error("missing ast analysis for %s", ast_str(node->k)); return -1; } -- cgit v1.2.3