It seems that when I upgraded the Fatou to julia 0.6 from 0.5, I needed to work around the new world counting feature in the julia language. It was possible to make Fatou functional in 0.6 by using the new invokelatest() function in the places where it was needed to run newly generated code. Howeve…

I know this is unintuitive but the type information you are providing is useless. The compiler can figure out those perfectly fine (assuming the code are properly generated). Even if compiler couldn’t figure out these info by itself, these uses of type assertions are as useful in 0.6+ with invokelat…

[image] "running in world age X, while current world is Y" errors General Usage No, simply defining the same function twice wouldn’t cause this — you can try it by modifying the task example I have above. In your case, the problem is likely the same as the simpler example…

So there is no way that the julia language could accept more specific information (theoretically) about the types in the new function, in order to speed up performance of such a function call? The programmer might know this information, the julia language would just have to be able to accept that in…

You could manually add type-assertions that allow Julia to make stronger assumptions about what the new versions of the function may return.

What source files in the julia code base would I need to look at if I wanted to try to implement this?

Also why do you claim it’s the invokelatest that’s causing the issue?

As @mbauman pointed out, using the invokelatest feature in this way does cause the code to slow down, since the type information cannot be inferred. I’d like to fix this in my own code, but as far as I know, the julia language does not yet let me provide the required type information when calling th…

[image] chakravala: As @mbauman pointed out, using the invokelatest feature in this way does cause the code to slow down Well, it’ll slow down compare to if you didn’t do runtime code generation. It won’t be slower than what you would otherwise get on <=0.5 [image] chakravala: the julia …

Have a look here at my source code: src/Fatou.jl (sym2fun(invokelatest(K.Q,Sym(:a),Sym(:b)),:(Complex{Float64})) |> eval)::Function I definitely provide the type information there Complex{Float64}, which is an argument to my sym2fun equation that generates the code that gets evaluated. Using sym2…

Yes, that makes sense, thanks for clarifying. Previously, having the type assertion at the return value of the function was sufficient to provide the output type. Now it was necessary to assert it in the function call as well: (matU[j,k],matF[j,k]) = invokelatest(nf,Z[j,k])::Tuple{UInt8,Complex{Flo…

Invokelatest() makes code run slower

Internals & Design

mbauman September 21, 2017, 3:46pm 2

Topic		Replies	Views
"running in world age X, while current world is Y" errors General Usage world_age	5	7611	September 15, 2017
World age problem General Usage question , world_age	20	3239	August 21, 2019
Codegen woes Performance	30	2417	August 27, 2019
Help for Base.invokelatest may be broken New to Julia	2	545	October 19, 2017
Creation of function using eval General Usage	7	1792	July 17, 2017

Invokelatest() makes code run slower

Related topics