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
I bumped into this weird bug when trying to make DataFramesMeta.jl pass its tests on 0.4 (FWIW, that happens in the thread_left() function.)
I've simplified the test case to this:
julia>functionf(x...)
call =Expr(x...)
end
f (generic function with 1 method)
julia>f(:a, :b)
ERROR: UndefVarError: call not defined
in f at none:2
The problem disappears if:
call is renamed to something else
another function than Expr is called
varargs are replaced with a fixed number of arguments
Using 'call' as a variable name currently triggers a bug in
Julia 0.4: JuliaLang/julia#11295
Work around it for now by using a different name.
Also get rid of deprecation warnings printed during the tests,
using Compat.jl where necessary.
I bumped into this weird bug when trying to make DataFramesMeta.jl pass its tests on 0.4 (FWIW, that happens in the
thread_left()
function.)I've simplified the test case to this:
The problem disappears if:
call
is renamed to something elseExpr
is calledCC: @tshort
The text was updated successfully, but these errors were encountered: