From 8680c4faf625477d6d1b79dc1db8f02f9548aa77 Mon Sep 17 00:00:00 2001
From: greg <greg.shuflin@protonmail.com>
Date: Fri, 16 Nov 2018 15:53:27 -0800
Subject: [PATCH] Just some notes for myself about how to redesign the AST type

---
 TODO.md | 15 ++++++++++++---
 1 file changed, 12 insertions(+), 3 deletions(-)

diff --git a/TODO.md b/TODO.md
index a4fb039..678d555 100644
--- a/TODO.md
+++ b/TODO.md
@@ -1,8 +1,20 @@
 
 # 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
 
+
 *A neat idea for pattern matching optimization would be if you could match on one of several things in a list
 ex:
 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