2.7 KiB
2.7 KiB
TODO
- Default cases (currently gets expanded to all constructors)
- Case for primitives
- aoc2023 translation
- some "real world" examples
- Maybe Eq and stuff would work for typeclass without dealing with unification issues yet
- unsolved meta errors repeat (need to freeze or only report at end)
- Sanitize JS idents, e.g.
_+_ - Generate some programs that do stuff
- import
- consider making meta application implicit in term, so its more readable when printed
- Currently we have explicit
AppsurroundingMetawhen inserting metas. Some people leave that implicit for efficiency. I think it would also make printing more readable. - When printing
Value, I now print the spine size instead of spine.
- Currently we have explicit
- eval for case (see order.newt)
- dynamic pattern unification (add test case first)
- switch from commit/mustWork to checking progress
- type constructors are no longer generated? And seem to have 0 arity.
- raw let is not yet implemented (although define used by case tree building)
- there is some zero argument application in generated code
- get equality.newt to work
- broken again because I added J, probably need to constrain scrutinee to value
- inline metas. Maybe zonk after TC/elab
- implicit patterns
- operators
- pair syntax (via comma operator)
- matching on operators
- top level
- case statements
- SKIP list syntax
- Agda doesn't have it, clashes with pair syntax
- autos / typeclass resolution
- We need special handling in unification to make this possible
- options
- keep as implicit and do auto if the type constructor is flagged auto
- keep as implicit and mark auto, behavior overlaps a lot with implicit
- have separate type of implict with
{{}} TypeClass.newtis the exercise for this
- do blocks
- some solution for
+problem (classes? ambiguity?) - show compiler failure in the editor (exit code != 0)
- write output to file
- uses
-ooption
- uses
- detect extra clauses in case statements
- add test framework
- decide what to do for erasure
- type at point in vscode
- repl
- LSP
- don't match forced constructors at runtime
- I think we got this by not switching for single cases
- magic nat (codegen as number with appropriate pattern matching)
- magic tuple? (codegen as array)
- magic newtype? (drop in codegen)
- records / copatterns
- vscode: syntax highlighting for String
Parsing
- consider allowing σ etc in identifiers
- Probably need to merge oper / ident first and sort out mixfix in parsing.
Background
- Read Ulf Norell thesis