Skip to content

vector-space-0.8.5 breaks compilation #27

Closed
peti opened this Issue Dec 8, 2012 · 2 comments

2 participants

@peti
peti commented Dec 8, 2012

After updating to the latest version of vector-space, I get the following build error:

Building diagrams-cairo-0.5.0.2...
Preprocessing library diagrams-cairo-0.5.0.2...
[1 of 5] Compiling Diagrams.Backend.Cairo.Internal ( src/Diagrams/Backend/Cairo/Internal.hs, dist/build/Diagrams/Backend/Cairo/Internal.o )
[2 of 5] Compiling Diagrams.Backend.Cairo.Text ( src/Diagrams/Backend/Cairo/Text.hs, dist/build/Diagrams/Backend/Cairo/Text.o )

src/Diagrams/Backend/Cairo/Text.hs:145:53:
    Couldn't match expected type `Point v0' with actual type `R2'
    In the return type of a call of `textSize'
    In the second argument of `(^+^)', namely `(textSize te)'
    In the second argument of `fromCorners', namely
      `(origin .+^ bearing te ^+^ (textSize te))'

src/Diagrams/Backend/Cairo/Text.hs:146:25:
    Couldn't match type `V b0' with `R2'
    Expected type: Envelope R2
      Actual type: Envelope (V b0)
    In the return type of a call of `getEnvelope'
    In the first argument of `setEnvelope', namely `(getEnvelope box)'
@byorgey
diagrams member
byorgey commented Dec 8, 2012

Thanks for the report! Do you get this error also when trying to build the HEAD version of diagrams-cairo?

@byorgey
diagrams member
byorgey commented Dec 10, 2012

Ah, never mind, I see that we do. For example, see https://travis-ci.org/diagrams/diagrams-doc/builds/3592682 .

@byorgey byorgey pushed a commit that closed this issue Dec 10, 2012
Brent Yorgey fix expression to work with new fixity of .+^ (fixes #27)
See conal/vector-space@f5ef4fd .  Note that
we could make use of the new left-associativity to omit some
parentheses here, which looks nice, but then we would have to jack up
the lower bound on vector-space (which, for consistency, we'd want to
do also on a bunch of other diagrams packages).  For now, the current
code should still compile with older versions of vector-space.
1592929
@byorgey byorgey closed this in 1592929 Dec 10, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.