This commit is contained in:
Mark Canlas 2023-01-20 14:58:39 -05:00
parent 018548e5c5
commit cce6fbc967
1 changed files with 9 additions and 0 deletions

View File

@ -29,3 +29,12 @@
- and then very late into register assignment (above) it would occupy N registers
- what if you model all functions using the same "bounce" area and then just use this as the canonical way to calculate stack depth
- this would maybe be "optimal" register allocation?
## Advanced vs basic interpreters
- Given "basic" elements `foo` and `bar`
- And given another advanced feature `superfoo`
- `foo` and `bar` should inhereit both `BasicInterpreter` and `AdvancedInterpreter`
- and `superfoo` should only inherit `AdvancedInterpreter`
- Then `superfoo` just be desugared into many `BasicInterpreter` blocks
- And then the interpretation for `foo` and `bar` under advanced just echos them as `BasicInterpreter`