Use 'fn' to define closure to make parsing/reading the language easier

It caused issues when you have parentheses to surround math expression,
for example: ((func() + 34) * 54)
is easier to parse if closure has to begin with 'fn'.

Also removed requirement for semicolons. Semicolons can't even be used
optionally yet.

1 files changed, 10 insertions, 0 deletions

diff --git a/src/tokenizer.c b/src/tokenizer.c
index 41d46fb..b996354 100644
--- a/src/tokenizer.c
+++ b/src/tokenizer.c
@@ -146,6 +146,13 @@ static CHECK_RESULT int __tokenizer_next(Tokenizer *self, Token *token) {
         self->value.identifier = create_buffer_view(self->code.data + identifier_start, self->index - identifier_start);
 
         switch(self->value.identifier.size) {
+            case 2: {
+                if(am_memeql(self->value.identifier.data, "fn", 2)) {
+                    *token = TOK_FN;
+                    return TOKENIZER_OK;
+                }
+                break;
+            }
             case 3: {
                 if(am_memeql(self->value.identifier.data, "var", 3)) {
                     *token = TOK_VAR;
@@ -324,6 +331,9 @@ static BufferView tokenizer_expected_token_as_string(Token token) {
         case TOK_STRING:
             str = "string";
             break;
+        case TOK_FN:
+            str = "fn";
+            break;
         case TOK_EQUALS:
             str = "=";
             break;