diff options
| author | Kimplul <kimi.h.kuparinen@gmail.com> | 2024-08-12 18:55:46 +0300 |
|---|---|---|
| committer | Kimplul <kimi.h.kuparinen@gmail.com> | 2024-08-12 19:06:03 +0300 |
| commit | 2157fdbaca0b80e488c4f77ad5c0d04b051175cf (patch) | |
| tree | 6a6ba7be30b2eb32219cd9aa2eb30c3bddacd5b4 /TODO | |
| parent | ce6ba9e8d260e43d11518688363229755a212472 (diff) | |
| download | ek-2157fdbaca0b80e488c4f77ad5c0d04b051175cf.tar.gz ek-2157fdbaca0b80e488c4f77ad5c0d04b051175cf.zip | |
make defer work better with generic code
Diffstat (limited to 'TODO')
| -rw-r--r-- | TODO | 8 |
1 files changed, 8 insertions, 0 deletions
@@ -35,3 +35,11 @@ main () * implicit conversion to pointer and passed as first argument, ufcs * does that for us. */ } + ++ Might want to add in some kind of suffix for integer types, s for i9 and l for +i27 or something? + ++ lowering could check if a function has been lowered and if not, lower it for +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. |
