language-cil

language-cil copied to clipboard

bamboo

Short branches

2

Should I add cases to OpCode for the short flavor of every branch? They all seem to have one, ``` Beq_s Label Bge_s Label Br_s Label Leave_s Label -- etc...

dmcclean

Maxstack calculation

4

Partition III, Section 1.7.4 requires correct CIL instruction sequences include a limit on the height the stack may reach during execution of that sequence. Relatedly, Section 1.7.5 requires that the...

dmcclean

There are a few aliases defined in the IL grammar in Partition VI, Annex C, Section C.1 et seq. ``` OPALIAS(CEE_BRNULL, "brnull", CEE_BRFALSE) OPALIAS(CEE_BRNULL_S, "brnull.s", CEE_BRFALSE_S) OPALIAS(CEE_BRZERO, "brzero", CEE_BRFALSE) OPALIAS(CEE_BRZERO_S,...

dmcclean

Is MethodDecl a good name?

2

Is `MethodDecl` really a good name for the construct that is currently named that? I agree that the production in the Partition VI, Annex C, Section C.3 grammar most closely...

dmcclean

Invented opcodes for named access to locals/arguments

4

There are a few invented opcodes in the Opcode type, which might not be the best thing to have if we want to parse CIL because the parser would have...

dmcclean

A monad for writing method bodies

5

The goal of making use of the library read as much like the resulting IL as possible, together with some issues around alpha-conversion, led me to this. Instead of writing...

dmcclean

A better AssemblyName / TypeName

3

Copied from [issue 2](https://github.com/tomlokhorst/language-cil/issues#issue/2/comment/748249): > The only other one I need in the near term is ldtoken, but it's a bit thorny because the current way of representing type (and...

tomlokhorst