> i do think it would be clearer, though, to explain up front that the module being built is not made of python code, but rather callable from python code
I know nothing about micropython. Do the modules contain bytecode?
I know nothing about micropython. Do the modules contain bytecode?
tools/mpy-tool.py lists opcodes: https://github.com/micropython/micropython/blob/master/tools...
Can the same be done with .pyc files; what are the advantages of MicroPython native modules?
Why does it need wasm2c?
- compile any language to wasm
- translate wasm to C99
- use the native target toolchain to compile C99 to .mpy
- run that on the device
But that doesn't solve for WASM on a MicroPython device.
And that is why smart contracts without costed opcodes could not be built on Python.
The conventional way of creating native modules for MicroPython is to write them in C. This work allows to use any language that supports WASM output target.