P. Oscar Boykin

tighter totality checking

1

if we have: ``` match foo: x@[_, _]: # this match is now total [a, b] = x gn(a, b) _: fn(foo) ``` We could potentially check this by propagating...

One issue we have in pattern matching totality checking is that difference is not exact. This is because: ``` _ - 1 = _ ``` If we could write `_...

make a list of normalization rules

8

We should make a doc listing all normalizations we can do: 1. we can inline lets (form of beta reduction, see below). 2. remove unused lets 3. push down a...

Track Pattern Regions

1

Anything we parse should keep the region it came from, but in particular, without knowing the Pattern regions, we can't give very nice error messages. The right way to do...

e.g.: ``` in file: test_workspace/AvlTree.bosatsu, package AvlTree, missing field height in Branch Branch {size: s } 17| match t: 18| Empty: 0 19| Branch { size: s }: s ^...

since we silently shadow, any values that don't typecheck, it might be worth noting if those names are shadowed locally since an easy kind of error to make is to...

implement a repl

1

most everything is in place, so this should be fairly easy. Related issues: #274 #431

add end of line comment support

1

We don't currently support things like: ``` x = 1 # this is always 1 ``` we have to write ``` # this is always 1 x = 1 ```...

if we use separate compilation, a package may have been compiled with a different version of a transitive dependency from another, which will yield ugly errors. We should check when...

If we move the order of definitions in a file, but it still compiles, the interface and compiled package should be identical. This can be done by doing a topological...