You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
KCVM is a low-level language, its instructions are usually generated by a compiler.
Problem
When debugging KCVM it's unclear why the high-level KCL generated a particular KCVM instruction.
Solution
Each Instruction should (optionally) support a comment string. That way compilers could explain "why" a particular instruction was included in the final instruction set.
Two suggested implementation approaches:
Adding a comment: Option<String> field to the Instruction type
Adding a map from instruction IDs to comment strings.
The KCVM debugger should show these comments.
Grackle should then add comments to the KCVM instructions it emits.
The text was updated successfully, but these errors were encountered:
Closes#205
The input JSON has been modified. Previously it accepted a Vec<Instruction>, now that is just one field of a JSON object.
The other field is a map from instruction indices to string comments. These comments show up in the debugger as events at the start of that instruction.
Background
KCVM is a low-level language, its instructions are usually generated by a compiler.
Problem
When debugging KCVM it's unclear why the high-level KCL generated a particular KCVM instruction.
Solution
Each
Instruction
should (optionally) support a comment string. That way compilers could explain "why" a particular instruction was included in the final instruction set.Two suggested implementation approaches:
comment: Option<String>
field to theInstruction
typeThe KCVM debugger should show these comments.
Grackle should then add comments to the KCVM instructions it emits.
The text was updated successfully, but these errors were encountered: