#14558: Unable to parse integer-gmp's Cabal file -------------------------------------+------------------------------------- Reporter: taylorfausak | Owner: hvr Type: task | Status: new Priority: normal | Milestone: Component: Core Libraries | Version: 8.2.2 Resolution: | Keywords: Operating System: Unknown/Multiple | Architecture: | Unknown/Multiple Type of failure: None/Unknown | Test Case: Blocked By: | Blocking: Related Tickets: | Differential Rev(s): Wiki Page: | -------------------------------------+------------------------------------- Comment (by taylorfausak): Clearly there was a bug in Stack. I'm not denying that. There was a bug in Stack, and it has been fixed. The solution for Stack users is to upgrade Stack. The core of my complaint and this ticket is:
it's frustrating that a core library is using a bleeding edge feature for basically no reason
It is demonstrably simple and easy to avoid using `^>=` constraints in core libraries. Doing so would ensure that the core libraries could be parsed with the greatest variety of tools. I think that is self-evidently good. As a thought experiment, consider what would happen if someone uploaded a `text-1.2.2.3` which was identical to `text-1.2.2.2` except that it specified `cabal-version: >= 2.0.1.1` instead of `cabal-version: >= 1.8`. Obviously the maintainers are well within their rights to make such a change. I am trying to argue that making a change like that is unnecessary and irresponsible. If such a change was made, I would encourage the maintainers to revert it. That's what I'm doing here. -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/14558#comment:24 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler