Consider getting rid of the [] symbols from the OpCodes in the source

[MichalMarsalek]

I refactored the code so that opcodes are now heavily used as object keys. However, the brackets in some of them mean that they cannot be used as identifiers in object literals nor dot access. So one does
return op.leq(a, b) but return op["eq[Int]"](a, b), {leq: "<="} but {"eq[Int]": "=="}.
I suggest we keep the brackets in the Polygolf frontend language, but rename the opcodes in the Polygolf typescript source. There are couple of ways of doing that. at_back[Ascii] could be referred to as

• at_back__Ascii
• at_back$Ascii
• at_back$Ascii$
• at_backAscii

[MichalMarsalek]

Nested objects have been suggested, so op.eq.Int(a, b) and {eq: {Int: "=="}}.