mtborg / d7050e Goto Github PK

Seems to be some problem with parsing negative signs in expressions.
foo(n-1)
causes some problems to fail, complaining aboout unrecognized token -1. Workaround is to put spaces around the '-' sign. Problem goes away when removing the possibility for numbers to parsed with a leading '-' sign.

The type checker seems to evaluate return statements in function arguments as valid return statements, i.e.
foo(return 1);
gets evaluated as
return 1;

let a = b;

most likely does not work.

At the moment this is not possible as lalrpop can't seem to handle raw string literals, i.e.
use crate::r#type::Type
fails.

Test more than just "is_ok()", e.g. test return values.

Should help a lot with debugging

fn foo() -> i32{ let a = 2;
should currently be possible but should not be.

Expression
true + true
should not be valid.

At the moment the boolean parser will mark

a == b == c

(which is not valid according to the rust compiler) as valid.

At the moment numbers are not allowed to be negative. This is easily fixed by allowing for a minus sign in the number-regex, although this would allow for expressions such as
let a = 2 + -2;
which does not look very nice.

The regex results in a false negative for the case when the identifier starts when an underscore and then a number (which should be allowed). Have not tested though.

Should give code location hints

Example:
foo(bar())

Probably wont work (haven't tested)

Some tests fail because what they test hasn't been implemented yet.