Does CodeTracking work inside of @compile_workload

[co1emi11er2]

I can't seem to get the @code_expr macro to work with PrecompileTools. I have tried using includet and importing module inside @compile_workload as well as @setup_workload. Nothing seems to work. It always returns nothing (things error when I try to use includet)

@setup_workload begin
    # Putting some things in `@setup_workload` instead of `@compile_workload` can reduce the size of the
    # precompile file and potentially make loading faster.
    using Revise
    using CodeTracking
    using TestHandcalcFunctions

    @compile_workload begin
        
        f = @code_expr calc_Ix(5, 15)
        println(f)

    end
end

Any thoughts?

[timholy]

I don't think this can work given current code organization. CodeTracking needs Revise for a lot of its functionality, and Revise gets activated on a package after module closure. That means it's too late to affect package precompilation, which happens before module closure.

What is it you're really trying to achieve?

[co1emi11er2]

Okay. Thanks for the quick response. I have a package that utilizes CodeTracking. It is called Handcalcs.jl. It uses CodeTracking to find functions and then it latexifies the expressions within the function, but I have never been able to figure out how to precompile the the parts of Handcalcs that use CodeTracking. A large function will take like 8 seconds to latexify the first time, and then it is fast after you run it again. Not a huge deal. I just thought I would ask. You can close the issue.

Here is an example of the part of Handcalcs that uses CodeTracking: Handcalcs.jl

[timholy]

Pretty cool.

but I have never been able to figure out how to precompile the the parts of Handcalcs that use CodeTracking

While CodeTracking needs Revise to populate some of its internal variables, there is no sense in which CodeTracking depends on Revise in a caller-callee sense. Consequently, one option is that you could use

using SnoopCompileCore
tinf = @snoop_inference # do something that's slow on first execution
using SnoopCompile, ProfileView
ProfileView.view(flamegraph(tinf))

and then look and see what's at the base of the flames and add an explicit precompile directive. You can also automate this, see https://timholy.github.io/SnoopCompile.jl/stable/tutorials/snoop_inference_parcel/