It's an embeddable scripting language with the goal of being a Rust-like language that supports hot reloading of functions AND data. To achieve the latter, it uses GC'ed memory such that memory can easily be mapped when the memory's type changes.
It's still in early development but maybe one day will serve your needs :)
Because how memory is allocated for a data structure is a separate decision from what data structure you want to use. When a variable is declared as a certain type, choosing where the memory is allocated makes sense, but to build it into the type itself is restricting the uses of it. It also raises questions about what happens when you want to copy something on the stack to an offset in an array of the same thing on the heap. Allocation should be completely separate from data structure declarations in my opinion.
It's an embeddable scripting language with the goal of being a Rust-like language that supports hot reloading of functions AND data. To achieve the latter, it uses GC'ed memory such that memory can easily be mapped when the memory's type changes.
It's still in early development but maybe one day will serve your needs :)