Ticket #25 (closed defect: fixed)

Opened 3 years ago

Last modified 3 years ago

vector shouldn't build-depend on ghc

Reported by: anonymous Owned by:
Priority: blocker Milestone: 0.7.0.1
Version: Keywords:
Cc:

Description

a package should build-depend on ghc only if it's using the ghc-api library, which comes in a package called "ghc". vector currently doesn't use that library but it's still needlessly tied to ghc via the dependencies stored by ghc-pkg, when installed, this makes it very vulnerable to a serie of issues related to the diamond dependency problem and eager shadowing based on ABI hash.

it should use the following instead:

if impl(ghc < 6.9)
    buildable: False

Change History

Changed 3 years ago by rl

Actually, vector does use ghc for SpecConstr annotations but these are only supported in 6.14 so it doesn't depend on ghc if built with 6.12. The Cabal file could probably express this. I'm curious about the problems you mention. If depending on ghc is bad we really ought to rethink the design of SpecConstr annotations. Could you please elaborate?

Changed 3 years ago by rl

  • priority changed from major to blocker
  • milestone set to 0.7.0.1

See http://hackage.haskell.org/trac/ghc/ticket/4387. SpecConstrAnnotation moved out of package ghc and into base so there is no need to depend on ghc any longer.

Changed 3 years ago by rl

  • status changed from new to closed
  • resolution set to fixed

Fixed in 0.7.0.1

Note: See TracTickets for help on using tickets.