What I meant was there needs to be constructs that guarantees that "this is going to be pure" and that "state can live here, not there".
D-lang has a start I believe, with a "pure" keyword.
I find that, as an enterprise developer working on large code base, most of my time is chasing bugs of silly null pointer exceptions and objects that are in unexpected state causing issues. Separating the grok of the code from the state eventually helps. And sadly there is little research spent in there, which is direct value to developers.
Increasing the quantity of pure code (and enforcing it) per class will reduce costly bugs.
I am amazed with what you can do though. I've had my shot at designing a language and miserably failed multiple times... But this why I'm raving about it... You may be able to solve this global problem that I never could.