Sebastián Mestre
Sebastián Mestre
This snippet makes desugaring crash. Instead, the parser should report an error. ``` y := 1 +; fn __invoke() => 0; ```
I added rudimentary testing for error paths on #303, but neglected to include them in CI. Of course, we should be running the error path test on CI, just like...
It would be pretty cool to have function that pretty-prints source code given an AST.
It would be pretty cool to be able to write something like ```c++ ErrorReport err = match_identifiers(...); if (!err.ok()) { Log::fatal()
## The Parser Whenever I go do a change in there, it all looks sloppily thrown together, not very exhaustive (I think I noticed a few places that don't handle...
To date, we have been just asserting that the conditions for a correctly-typed program were true. This gives a really bad user experience: The release build will not display an...
We have no way to write the type of a function: no special syntax, and no name bound to the typefunc. We need this. a few options: ```rust (a,b,c)=>d fn(a,b,c)=>d...
Right now, there is no way to explicitly mark anything as polymorphic. There really should be. I was thinking it could look like this (I made up the syntax for...
As discussed on #324, there are a lot of legacy issues in the typechecker that make it buggy and more complex than it needs to be. Here are some ideas...
It's pretty lame that the test runner can only run until one test crashes. It would be really cool if it could handle crashes and print a nice summary. Not...