Krustlet Provider about firefly

[bitwalker]

In theory all it should require is the ability to compile to wasm32-wasi as a target, which is what our wasm support needs to target anyway. Beyond that, it would probably be necessary to implement bindings to the host-provided APIs as a NIF, but I haven't looked into what all is offered or required to support there.

Support for this kind of thing is down the road a way yet, we're focusing on full support for native targets first (x86_64/arm64), then fleshing out the wasm32 support once we know the full set of things required to bootstrap a native Erlang/Elixir executable on such a restricted target. But per your question, aside from the ability to target wasm32, I don't think there is any other restrictions on using a Firefly-compiled executable as a krustlet provider.

[sleipnir]

Thank you @bitwalker for your answer