I don't understand, why is allocation not part of IO? This seems like effect oriented programming with a kinda strange grouping: allocation, and the rest (io).
Most effect-tracking languages have a GC and allocations/deallocations are handled implicitly.
To perform what we normally call "pure" code requires an allocator but not the `io` object. Code which accepts neither is also allocation-free - something which is a bit of a challenge to enforce in many languages, but just falls out here (from the lack of closures or globally scoped allocating/effectful functions - though I'm not sure whether `io` or an allocator is now required to call arbitrary extern (i.e. C) functions or not, which you'd need for a 100% "sandbox").
Remember to look for critical takes. I encourage you to look at stuff like this with an open mind, and if you disagree with anything, look into the details:
I'm not sure how these "language models" perform. I went to the Bosnian model, but for some reason I got a demo that could analyze Danish? The site does not mention anything about the performance of the models. (At least I could not find that information)
