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?

1 files changed, 44 insertions, 0 deletions

diff --git a/src/ast.c b/src/ast.c
index 119f943..81fa0b3 100644
--- a/src/ast.c
+++ b/src/ast.c
@@ -604,3 +604,47 @@ bool type_lists_match(struct type *al, struct type *bl)
 	}
 	return true;
 }
+
+const char *ast_str(enum ast_kind k)
+{
+#define CASE(x) case x: return #x;
+	switch (k) {
+	CASE(AST_CLOSURE);
+	CASE(AST_IF);
+	CASE(AST_LET);
+	CASE(AST_INIT);
+	CASE(AST_CALL);
+	CASE(AST_PROC_DEF);
+	CASE(AST_VAR_DEF);
+	CASE(AST_DOT);
+	CASE(AST_BLOCK);
+	CASE(AST_ID);
+	CASE(AST_EMPTY);
+	CASE(AST_ADD);
+	CASE(AST_SUB);
+	CASE(AST_MUL);
+	CASE(AST_DIV);
+	CASE(AST_REM);
+	CASE(AST_LAND);
+	CASE(AST_LOR);
+	CASE(AST_LSHIFT);
+	CASE(AST_RSHIFT);
+	CASE(AST_LT);
+	CASE(AST_GT);
+	CASE(AST_LE);
+	CASE(AST_GE);
+	CASE(AST_NE);
+	CASE(AST_EQ);
+	CASE(AST_NEG);
+	CASE(AST_LNOT);
+	CASE(AST_NOT);
+	CASE(AST_CONST_INT);
+	CASE(AST_CONST_CHAR);
+	CASE(AST_CONST_BOOL);
+	CASE(AST_CONST_FLOAT);
+	CASE(AST_CONST_STR);
+	}
+#undef CASE
+
+	return "UNKNOWN";
+}