I have a strong preference for fast compilation, but the trade-off with analysis is not so straightforward.
Just finishing compilation is not sufficient to find problems, testing is needed too; if compilation and analysis can be done faster than compilation and testing, then you can still come out ahead.
I think SBCL shows that there's a decent amount of low hanging fruit for analysis; it catches a surprising number of errors with reasonably fast compilation (incremental compilation of dozens of functions feels instant), and notes places where the code could be restructured to allow for better analysis.
Just finishing compilation is not sufficient to find problems, testing is needed too; if compilation and analysis can be done faster than compilation and testing, then you can still come out ahead.
I think SBCL shows that there's a decent amount of low hanging fruit for analysis; it catches a surprising number of errors with reasonably fast compilation (incremental compilation of dozens of functions feels instant), and notes places where the code could be restructured to allow for better analysis.