| | 132 | |
| | 133 | === How will addressing work? Will there be a different instruction for local goto vs far-away goto?* === |
| | 134 | === How will CPS work if all we have is goto?* === |
| | 135 | === How will security work?* === |
| | 136 | === What is Lorito's concept of memory vs registers? There seems to be an assumption there, but it's not documented.* === |
| | 137 | === What will Lorito have that will give us flexibility equivalent to C's pointers? More concretely, what will the data structure for RPA look like?* === |
| | 138 | |
| | 139 | === How can we fix freeze/thaw so that rakudo can use it to decrease its startup time?** === |
| | 140 | === How tightly-defined are PMCs in Lorito, i.e. are they more like structs or chunks of memory? Will there be a way for Lorito to generically understand PMC guts, especially references to other PMCs?** === |
| | 141 | === How will composed ops work, both on a VM level and in bytecode?** === |
| | 142 | === How will Lorito code be translated for stack VMs?** === |
| | 143 | === The object metamodel is important, especially since Object and PMC will be covered by the same concept. If we're not using P&W, we need to nail down what we are going to use.** === |
| | 144 | |
| | 145 | === Is there value in an op to move a value between memory locations?** === |
