Jaro

This is caused by the new way cabal does things. An ugly workaround is to run `cabal v2-install --lib --package-env . plugins` in the directory that you're working in (or...

I agree that this could be improved. There's not much to debate, so I'd say you can immediately [open a GHC issue](https://gitlab.haskell.org/ghc/ghc/-/issues/new) about this.

@scarf005 my initial reaction was that it seems like that such extended messages are more suitable for the [error message index](https://errors.haskell.org). However, one disadvantage of that is that it only...

That's a good point. Still, I'd be tempted to say the best solution to that problem is to improve how the HLS `typecheck` command works.

That makes sense, I've opened https://github.com/haskell/cabal/issues/8540.

@mpscholten that proposal doesn't seem to be implemented yet. I think we should keep issues here open until the improvements have actually been incorporated in a released version of GHC.

Actually, now I'm also thinking that we can suggest possible constructors if we know the type of the thing we're matching against. That would be similar to the valid hole...

> Really, I think what would be best for the particular complaint you linked to is to have a web page for every error, explaining it in more detail and...

> On the topic of links/urls in error messages: I think that there should be one page for the general error message and then on that page there might be...

There is now also [another error reported on discourse](https://discourse.haskell.org/t/making-a-parse-error-when-learning-about-index-functions/2848?u=jaror) that has another extra angle, namely that the `Main` module is mentioned while it is never explicitly declared by the user...