You’d be compiling the majority of other options too for embedded, so that’s not really a drawback.
Architecturally speaking, it makes almost no sense to have dynamic memory allocation in Microvium. You could theoretically even do static analysis on whatever chunk of code you're about to run and figure out exactly what your upper bound for memory usage would be. (Remember, we don't have an interactive runtime.)
So now that I actually think about it more, not pre-allocating in this particular case is actually an antipattern.
> In typical firmware, idle memory is much more important than peak memory, as I explained in my last post.
https://coder-mike.com/blog/2022/05/27/single-threading-is-m...