interfaces VS gluon

I like how wasmCloud does things - they define the interface using smithy like this https://github.com/wasmCloud/interfaces/blob/main/httpserver/httpserver.smithy (in the httpserver interface, the wasm side receives http requests as structs, and replies with responses as structs. The native-code side is responsible for listening on the TCP port etc. There are a bunch of other first-party interfaces, including an httpclient interface, for outgoing requests initiated by wasm). They then generate basic interface code for all supported languages from the smithy definitions. They also hand-write some helper functions, to make things easier on the wasm side (this isn't the same from language to language - there are more helpers for rust than other languages).

A colleague of mine used https://github.com/gluon-lang/gluon with great success in our rust projects. Although it probably can't run in a no_std environment.

Aside from these, if you want some inspiration for a production-grade language built in Rust, you might want to go through the source code of Starlark and Gluon.

Some languages, like Zig and Gluon have an import expression, where the imported symbols are under a local constant's name. Gluon then also supports destructuring, and Zig has had multiple proposals for years about it, none of which are canon. That is, code like this:

This should be a good use-case for rust-based scripting languages, I think.

I loosely followed a project of that kind a while ago, I don't quite remember if it was Gluon [0] or Dyon [1]. Not sure if these are still active, or if another competitor showed up in meantime.

___

[0] https://github.com/gluon-lang/gluon

[1] https://github.com/PistonDevelopers/dyon

Or if you wanted something more Rust-native, you could try Gluon.

Gluon