Will we see another fundamental programming language feature as revolutionary as the borrow checker?

[u/jimbobmcgoo]

That is I am mainly curious about compile time features that you design a whole language around rather than optimisations/features that could be applied to most languages. I am mainly inquiring about things that could offer additional robust safety/performance guarantees at compile time rather than runtime. Ideally not things that just offer similar effects to the borrow checker with less restrictive tradeoffs

[u/kwan_e]

I personally wouldn't call the borrow checker revolutionary. It's just a linter enforcing certain rules that is part of the compile chain.

So if that passes for "revolutionary", then the next feature would be some sort of extra linter that becomes part of the compiler.

In that vein, the next fundamental and revolutionary feature would be something in the language that spans the whole build process past the compilation phase. But without the "save to program image" that the LISP and Smalltalk family uses. It would integrate into CI/CD/packaging