upvote
Not even, regarding type systems, see D or Ada compilers.

Or if you prefer to travel back to 1993, here is a developer experience using C++ as if it was Lisp Machine/Smalltalk environment with incremental compilation and hot code reloading.

"Lucid Energize Demo"

https://www.youtube.com/watch?v=pQQTScuApWk

With one of the very first ideas of a LSP could be like,

https://dreamsongs.com/Files/Energize.pdf

We got into a culture that accepted slow compilers is normal, it doesn't have to be.

reply
One of the noteworthy papers I remember reading in the early 90's was a demonstration that you could even add SSA form to ETH's Oberon compiler to apply optimisations equivalent to the then-current version of gcc with very little loss in compilation speed.

I guess today if you want fast, optimized codegen you need to look more at JIT research since it seems the AOT compiler research seems as you say to have just accepted that slow compilers is normal.

reply
Yes, spot on.

A good mix is having a JIT/AOT combo, use JIT for the development workflow, and a full blown AOT with all possible optimisations turned on for production releases.

reply
Not really. In addition to Ada and D mentioned by a sibling comment, Ocaml or F# have even richer type systems than Rust, and compile times are better.

Yes, compiling Rust in the release mode could take long time and it would be worth all this baggage - monomorphization, trait resolution etc. But there is no reason, except not giving shit, to no have a fast and simple pipeline for debug builds.

reply