Immediately fail on GHC mismatch

alexwl / haskell-code-explorer

Web application for exploring and understanding Haskell codebases

MIT License

509 stars 20 forks source link

Immediately fail on GHC mismatch #40

Closed seagreen closed 5 years ago

seagreen commented 5 years ago

I ran haskell-code-explorer on a medium size project and got huge wall of error output. When I started up haskell-code-server only a few modules had been indexed.

It turns out the culprit was a GHC version mismatch, but I hadn't noticed the problem because the notification about it was scrolled of the screen.

Might a better default be to fail immediately when a GHC mismatch is detected?

alexwl commented 5 years ago

I agree it's better to fail immediately.

An attempt to index the package when versions of GHC don't match is a mistake.