JuliaDebug / JuliaDebug/SnoopCompile.jl
compatibility code for v1.0
Open
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 331
- Forks
- 58
- Avg merge
- 2h 35m
- Merged PRs (30d)
- 7
Description
I've written this snippet of code for inclusion in PackageCompiler.jl, but it feels like it should belong somewhere here.
let M = Module() # Prevent this from putting anything into the Main namespace
# get a local reference to any module that may be directly referenced in the `precompile.jl` file
for m in Base.loaded_modules_array()
Core.isdefined(M, nameof(m)) || Core.eval(M, Expr(:const, Expr(:(=), nameof(m), m)))
end
for n in names(Main)
if Core.isdefined(Main, n) && isconst(Main, n)
m = getfield(Main, n)
m isa Module && (Core.isdefined(M, nameof(m)) || Core.eval(M, Expr(:const, Expr(:(=), nameof(m), m))))
end
end
Base.include(M, \"precompile.jl\")")
end # let
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the compatibility snippet in the issue and how it relates to PackageCompiler.jl and the precompile.jl entry point. Determine where this logic could belong in SnoopCompile.jl and whether it can be integrated without polluting Main; done means the ownership and integration approach are settled and the compatibility behavior is covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100