jacoobes / nums Goto Github PK

Currently having issues that track the location of the error while parsing.
For example,

package a //packages are supposed to end in semicolons

     fun foo| a: str| {}

Error :

Expected Semi, got Function
src/main.nums:5:7

     fun foo|a:str| {}
        ^

The error reporting is nowhere near accurate

blocks can act as an expression also, returning an expression at the end. It'ss sorta like an iife from js

Implement better error handling for the first stage of parsing.

Need a way for Nums to track the file that's currently being parsed/ compiled so it contributes to a cleaner error handling. I already have lines and the basic location of where the error is. Need file location.

I feel like Span maybe too restricted to just the first stage parser, might need to implement a trait to share logic between different span types for different parsing stages

I was lazy and only printed out ASTs instead of asserting they were correct. Need some help making assert statements to unit test the AST nodes correctly.

 fn power() {
        let text = "5 ^ 10 + 16 + 3;";
        let tree= create_tree(text);
        match tree {
            Ok(e) => println!("{:?}", &e),
            Err(span) => println!("{:?}", span)
        }
    }

For example, I'm just printing out instead of asserting.

simply put, diversify how spans are created. Some errors, such as NoTopLevelDeclaration do not need specific line by line detail.