You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: TODO.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,10 @@
2
2
## TODO
3
3
4
4
-[x] Take the parens off of FC to make vscode happy
5
+
-[x] Magic to make Bool a boolean
6
+
-[ ] Look into using holes for errors (https://types.pl/@AndrasKovacs/115401455046442009)
7
+
- This would let us hit more cases in a function when we hit an error.
8
+
- I've been wanting to try holes for parse errors too.
5
9
-[ ] in-scope type at point in vscode
6
10
- So the idea here is that the references will be via FC, we remember the type at declaration and then point the usage back to the declaration (FC -> FC). We could dump all of this. (If we're still doing json.)
7
11
- Do we want to (maybe later) keep the scope as a FC? We could do scope at point then.
@@ -29,7 +33,7 @@
29
33
-[ ] Add `export` keywords
30
34
-[ ] vscode - run newt when switching editors
31
35
-[ ] who calls X? We can only do this scoped to the current context for now. Someday whole source dir. #lsp
0 commit comments