Update TODO
This commit is contained in:
parent
f4029fe31a
commit
ff1d4ef7bb
5
TODO.md
5
TODO.md
@ -23,9 +23,6 @@
|
|||||||
|
|
||||||
2. Once FQSNs are aware of function parameters, most of the Rc<String> things in eval.rs can go away
|
2. Once FQSNs are aware of function parameters, most of the Rc<String> things in eval.rs can go away
|
||||||
|
|
||||||
## Parser
|
|
||||||
* I think I can restructure the parser to get rid of most instances of expect!, at least at the beginning of a rule
|
|
||||||
|
|
||||||
## Typechecking
|
## Typechecking
|
||||||
|
|
||||||
* make a type to represent types rather than relying on string comparisons
|
* make a type to represent types rather than relying on string comparisons
|
||||||
@ -44,8 +41,6 @@
|
|||||||
|
|
||||||
## Language Syntax
|
## Language Syntax
|
||||||
|
|
||||||
* a type like `type Klewos = Klewos { <fields> }` (i.e. a type with exactly one record-like variant) should be writeable as
|
|
||||||
`type Klewos = { <fields> }` as a shorthand, and should not require explicit matching.
|
|
||||||
* the `type` declaration should have some kind of GADT-like syntax
|
* the `type` declaration should have some kind of GADT-like syntax
|
||||||
* use `let` sigil to indicate a variable in a pattern explicitly:
|
* use `let` sigil to indicate a variable in a pattern explicitly:
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user