duckscript VS gluon

Currently i'm using it in cargo-make but will also use it later to parse args for duckscript commands.

At it's most basic you could make a really simple interpreter by just doing such a thing, and there is essentially already such a simple language like that built for/in rust called Duckscript (rust has a surprisingly large number of little embedded languages), and that would be completely and entirely sufficient for many purposes, though if you want speed then you'll need to JIT or AOT the code, which is why wasm is so handy as you can interpret or JIT (or even AOT it with wasmer) without the much larger overhead of a, for example, javascript or java embedded runtime.

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