greg/schala
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Just some notes for myself about how to redesign the AST type

Browse Source
This commit is contained in:
greg 2018-11-16 15:53:27 -08:00
parent b198984fc5
commit 8680c4faf6
1 changed files with 12 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
TODO.md
View File

@ -1,8 +1,20 @@
# TODO Items # TODO Items
-Plan of attack:
-write a visitor pattern for AST
-convert AST type to including SourceMap'd wrappers (w/ .into())
-at the same time, amke sure the visitor pattern "skips over" the SourceMap'd stuff
so it can just care about AST structure
- AST : maybe replace the Expression type with "Ascription(TypeName, Box<Expression>) nodes??
- parser: add a "debug" field to the Parser struct for all debug-related things
-scala-style html"dfasfsadf${}" string interpolations!
-fuzz test schala -fuzz test schala
*A neat idea for pattern matching optimization would be if you could match on one of several things in a list *A neat idea for pattern matching optimization would be if you could match on one of several things in a list
ex: ex:
if x { if x {
@ -102,10 +114,7 @@ type enum {
- AST : maybe replace the Expression type with "Ascription(TypeName, Box<Expression>) nodes??
- parser: add a "debug" field to the Parser struct for all debug-related things
-scala-style html"dfasfsadf${}" string interpolations!
*Compiler passes architecture *Compiler passes architecture