Thanks for the response!

My main critique - which I'm sure you're aware of - is that the hardest part of doing this is predicting what your workload is actually going to be like. That's what Go does so well. It can get almost anything right without you needing to hand-tune it.

While I have you - are y'all planning to implement FSMs and thunks (for recursion) at any time in the near future?

This is something Go is unlikely to ever do unless it becomes a Go2 language.

I don't know enough about your runtime to know if it's remotely feasible given the choices you've made.