You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
src/Graphics/SVGFonts/Text.hs:53:35: error:
Ambiguous occurrence ‘Default’
It could refer to
either ‘Data.Default.Class.Default’,
imported from ‘Data.Default.Class’ at src/Graphics/SVGFonts/Text.hs:34:1-25
or ‘Diagrams.Prelude.Default’,
imported from ‘Diagrams.Prelude’ at src/Graphics/SVGFonts/Text.hs:35:1-68
(and originally defined in ‘data-default-0.8.0.0:Data.Default.Internal’)
|
53 | instance (Read n, RealFloat n) => Default (TextOpts n) where
I think that recent revisions to diagrams ecosystem related to data-default-0.8 major breakage were handled too softly.
As Default is part of external interface, it's just created a mess.
Latest diagrams-lib uses data-default, but SVGFonts depends on data-default-class. Old data-default-class and new data-default can co-exist, which causes install plans like above having two different Default in scope possible.
IMHO the only clean solution is to have major releases of everything (withDefault in public API), and only use the later data-default. data-default change was big and disruptive, I don't see a way to go around it in non-major way.
The text was updated successfully, but these errors were encountered:
I think that recent revisions to
diagrams
ecosystem related todata-default-0.8
major breakage were handled too softly.As
Default
is part of external interface, it's just created a mess.Latest
diagrams-lib
usesdata-default
, butSVGFonts
depends ondata-default-class
. Olddata-default-class
and newdata-default
can co-exist, which causes install plans like above having two differentDefault
in scope possible.IMHO the only clean solution is to have major releases of everything (with
Default
in public API), and only use the laterdata-default
.data-default
change was big and disruptive, I don't see a way to go around it in non-major way.The text was updated successfully, but these errors were encountered: