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
Due to JuliaLang/julia#6190, v0.5 throws a MethodError when function calls are ambiguous. This has come up recently in #881 and in #871. This kind of error is everywhere where we have aliased geometries (e.g. histogram, path, etc):
Non-aliased geometries work fine. Currently, the only way around this is by changing Geom.histogram to Geom.histogram(), which prevent the ambiguity by returning a Geometry object instead of a Function. This error is due to the untyped a and b in (::Gadfly.#kw##plot)(::Array{Any,1}, ::Gadfly.#plot, f::Function, a, b, elements::Union{DataType,Function,Gadfly.Element,Gadfly.Theme}...) causing issues when dispatching.
The text was updated successfully, but these errors were encountered:
Due to JuliaLang/julia#6190, v0.5 throws a
MethodError
when function calls are ambiguous. This has come up recently in #881 and in #871. This kind of error is everywhere where we have aliased geometries (e.g.histogram
,path
, etc):Non-aliased geometries work fine. Currently, the only way around this is by changing
Geom.histogram
toGeom.histogram()
, which prevent the ambiguity by returning aGeometry
object instead of aFunction
. This error is due to the untypeda
andb
in(::Gadfly.#kw##plot)(::Array{Any,1}, ::Gadfly.#plot, f::Function, a, b, elements::Union{DataType,Function,Gadfly.Element,Gadfly.Theme}...)
causing issues when dispatching.The text was updated successfully, but these errors were encountered: