[Design and Implementation] ISL Interpreter

[alpaylan]

The interpreter's task is to

• given a parsed instruction,
• type-check the instruction
• compile the instruction to the move(function call to canvas API)

The complex part is (clearly) the type-check. Luckily we can use a dynamic type-system. We will need to do a number of checks regarding operations. For each instruction, questions arising include but not limited to;

• Does the given block, pixel or color exist?
• Do the given blocks swappable?
• Do the given blocks mergable?
• Do the given block cuttable or colorable with the given instruction?

@gambasz will be in charge of this.

Guido, in my head the task is;

• Define the relevant questions and document them.
• Define formal definitions of those questions.
• Implement the interpreter using these questions.

You can define your own structures inside javascript assuming parser will provide them to you, we will make the connection.

Before you start implementing, we will need a canvas implementation. Which @umut-sahin is gracefully implementing for the back-end and someone(possibly I or Umut again) will port for the front-end.

[gambasz]

Here's what I think might be a good start into addressing the first two points. There are some questions we still need to answer (clarify and standardize) but for the most part I think we'll be ready to start once the canvas is ready. Attached is a rough draft to get us started:

Typechecking_ISL.pdf

[alpaylan]

Typechecking_ISL.pdf

I tried to answer some of the questions here. Does this make sense. I'm writing the participant spec; which tries to be more clear. Maybe reading that could be helpful?

ICFP Contest 2022.pdf

[gambasz]

Comments definitely make sense. I can get started on the checks that don't directly require the use of the canvas.