Hackathon Development Roadmap

[alexanderkyte]

Things between now and an MVP:

 0. Write system for making basic blocks when running into Control Instructions. We need the labels for the C# control flow logic. 

1. Finish straight-line codegen translation of non-memory + non-table opcodes. Have test that doesn't use those systems. 

2. Write table+memory systems, use static constructors and arrays

3. Finish writing parser for export/import tables.

4. Set up testing harness with real-world applications.

5. Define embedding API that allows both SRE+Save and SRE+Run. Webassembly is sandboxed, so this admits a "take URL and lazily fetch code" strategy. 

6. Create logging system to better report compilation / format errors (machine 2 machine so less of a concern than for a normal compiler)

[alexanderkyte]

The design document that makes this parsing work most productive for me thus far has been here: https://webassembly.github.io/spec/core/binary/modules.html

[alexanderkyte]

3. Finish writing parser for export/import tables.

• William Cummings plans to own this component

[alexanderkyte]

5. Define embedding API that allows both SRE+Save and SRE+Run. Webassembly is sandboxed, so this admits a "take URL and lazily fetch code" strategy. 

• Katelyn Gadd plans to own this component

[alexanderkyte]

 0. Write system for making basic blocks when running into Control Instructions. We need the labels for the C# control flow logic. 

1. Finish straight-line codegen translation of non-memory + non-table opcodes. Have test that doesn't use those systems. 

I (alexanderkyte) plan to own this component

Development done here: https://github.com/alexanderkyte/Wasm2CIL/tree/opcode_emit

[alexanderkyte]

Webassembly needs javascript glue to work properly. I think this interpreter should be perfect for glue init.
https://github.com/sebastienros/jint