diff options
| author | Kimplul <kimi.h.kuparinen@gmail.com> | 2026-08-02 15:40:58 +0300 |
|---|---|---|
| committer | Kimplul <kimi.h.kuparinen@gmail.com> | 2026-08-02 15:40:58 +0300 |
| commit | 4580e74f54e22a81f8b5f40639518247ee37d1c5 (patch) | |
| tree | 471e3fe1ef11d9e7dbc66597245a5ca0fd38ed52 | |
| parent | a986dfc17093ae5b7a33a8fffecd2cabf49deee3 (diff) | |
| download | fwdscript-4580e74f54e22a81f8b5f40639518247ee37d1c5.tar.gz fwdscript-4580e74f54e22a81f8b5f40639518247ee37d1c5.zip | |
add TODO about stackful uses
+ Better to implement of course, but I just wanted the thought out of my
head for now
| -rw-r--r-- | TODO | 14 |
1 files changed, 14 insertions, 0 deletions
@@ -0,0 +1,14 @@ +feck, groups do need some kind of stackful handling, since something like + + guard c err ok { + if c { + ok + } { + err + } + } + +has a hierarhcy, where if we just linearly go through it we mark `ok` as used +and then `err` gets used as well, not ideal. Luckily easily fixed, just create a +new stack element for each closure and run stuff locally within it, no need to +merge results (yet) |
