I'd say GHC has it right in this case.
(f a ~ g b) exactly implies (f ~ g) and (a ~ b) if and only if the kinds match
up. If, say, (f :: k1 -> *), (g :: k2 -> *), (a :: k1), and (b :: k2), then (f
~ g) and (a ~ b) are ill-kinded. In Gabor's initial problem, we have (with all
type, kind, and coe
Hi,
The problem in https://github.com/haskell/cabal/issues/1611 is with
that we have a module (say, A) from which we're only importing a
single value, and this module is a part of the cabal-install source
tree. It would be nice if the whole contents of A weren't linked with
the final executable. S
Hello,
The upcoming GHC 7.8 recently gave me this error:
Could not deduce (i ~ i1)
from the context (f1 i ~ f i1)
Which is strange to me: shouldn't (f1 i ~ f i1) exactly imply (f1 ~ f,
i ~ i1)? (Or with nicer variable names: (f a ~ g b) => (f ~ g, a ~
b)?)
When I inquired about this in
On Wed, Dec 18, 2013 at 10:27 AM, harry wrote:
> Brandon Allbery wrote
> > I don't understand the question. Whether a library is split-objs or not
> > does not affect how you link an executable, only the space/time
> efficiency
> > trade-off of doing so. And while in theory you might see improvem
Brandon Allbery wrote
> I don't understand the question. Whether a library is split-objs or not
> does not affect how you link an executable, only the space/time efficiency
> trade-off of doing so. And while in theory you might see improvements by
> split-objs-ing an executable, it doesn't make a w
On Wed, Dec 18, 2013 at 4:08 AM, harry wrote:
> The documentation for --split-objs states that "this only makes sense for
> libraries". How is an executable compiled against a split-objs library?
> According to
> https://github.com/haskell/cabal/issues/1611#issuecomment-30750655, this
> isn't hap
The documentation for --split-objs states that "this only makes sense for
libraries". How is an executable compiled against a split-objs library?
According to
https://github.com/haskell/cabal/issues/1611#issuecomment-30750655, this
isn't happening by default.
--
View this message in context:
ht
