Cabal VS error-message-index

Also, there's already a cabal RFC to support toml: https://github.com/haskell/cabal/issues/7548

Cabal has a lot of dark corners once you stray from the happy path. Just checked and I'm currently subscribed to 37 threads on the issue tracker, and I'm not a maintainer. A lot of these are related to lesser-used features like cabal scripts, environment files and doctests (though I think all of these things would used more if they were more reliable), but there's also plenty of stupid stuff like: - https://github.com/haskell/cabal/issues/3313 - https://github.com/haskell/cabal/issues/8527 - https://github.com/haskell/cabal/issues/8391 - https://github.com/haskell/cabal/issues/7789 - https://github.com/haskell/cabal/issues/6888 - https://github.com/haskell/cabal/issues/6999 - https://github.com/haskell/cabal/issues/5271

Given that Mike Pilgrim (the Stack maintainer) is on Windows, and Cabal has issues on Windows, I think it might be easier to get Windows specific fixes merged in Stack.

The error message is not too helpful. This is the target of a long-standing ticket: https://github.com/haskell/cabal/issues/7993 Your help would be very welcome.

By the way, there are some open issues for the command to add a package in Cabal.

That's interesting. Could you could open a an issue about this? https://github.com/haskell/cabal/issues

I created this issue a few months ago: https://github.com/haskell/cabal/issues/8270

Reported this as a bug in cabal.

We definitely plan to have benchmarks once we start working on performance. We haven't started yet because there were more urgent tasks. For example: ensuring that the testsuite runs on CI with the JS backend (should be completed this week or the next), ensuring that the toolchain works properly (we're writing a tutorial and we've found new bugs, e.g. yesterday I've fixed the support for js-sources in Cabal https://github.com/haskell/cabal/pull/8636), adding TH support...

Significant effort is going into resolving this issue right now and things should be much improved in 9.6. We already have https://errors.haskell.org/ which catalogues many errors with descriptions and examples. The asspciated error codes will be added to all errors once 9.6 is release for easy reference.

We're also delighted to announce integration with errors.haskell.org, which already has a couple of GHCup codes documented, e.g. https://errors.haskell.org/messages/GHCup-00010/

To support the Haskell Foundation’s Haskell Error Index initiative, all Stack error messages generated by Stack itself begin with an unique code in the form [S-nnnn], where nnnn is a four-digit number.

I don't think the resolved issues are actually ones about error messages. They largely seem to be meta issues about the project. As far as I know nothing that project has done has made it into a released GHC yet, but GHC 9.6 will have unique error codes for each error pointing to an entry on https://errors.haskell.org/. Both the codes and the website are achievements of that project, specifically under its error-messages-index incarnation. If you'd like to contribute you may like to read https://github.com/haskellfoundation/error-message-index/blob/main/CONTRIBUTING.md or post a message introducing yourself on https://github.com/haskell/error-messages/issues/new.