diff options
| author | Kimplul <kimi.h.kuparinen@gmail.com> | 2024-08-12 19:01:21 +0300 |
|---|---|---|
| committer | Kimplul <kimi.h.kuparinen@gmail.com> | 2024-08-12 19:06:03 +0300 |
| commit | 6385450ddba34bc28bd7492d126fd38cb3f86f36 (patch) | |
| tree | 25717c5d13e67207932bdc6393da7807720b2f6d /TODO | |
| parent | 29c6d398d22d633425177400f34ab508260f02bf (diff) | |
| download | ek-6385450ddba34bc28bd7492d126fd38cb3f86f36.tar.gz ek-6385450ddba34bc28bd7492d126fd38cb3f86f36.zip | |
make id scope point to defining scope
+ Allows defers to refer to the correct scope, but
might be a bit surprising since effectively all other
nodes use the scope to refer to the containing scope
rather than the defining scope.
Diffstat (limited to 'TODO')
| -rw-r--r-- | TODO | 7 |
1 files changed, 7 insertions, 0 deletions
@@ -43,3 +43,10 @@ i27 or something? us. Should it also check that no abstract data types are used in the final lowering? Which would mean that even the lowering is allowed to fail, and not just the actualization phase. + ++ continue/break could probably fairly easily use labels as well, just check +that the following AST node is a loop and treat is as the name for that loop. +Then continue just goes to the bottom of the loop and break goes out of the +loop, pretty much what we're currently doing but just with the top loop +in the stack. We'd probably just have to check the loop stack in lower.c, +should be fairly straightforward? |