JuliaDebug / JuliaDebug/Cthulhu.jl
Handling invokelatest
Open
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 709
- Forks
- 46
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 2
Description
f() = @debug "debug"
We see in the IR a:
3 ── %13 = π (%9, Base.CoreLogging.AbstractLogger) ││
4 ── %14 = Core._call_latest(Base.CoreLogging.shouldlog, %13, $(QuoteNode(Debug)), Main, Symbol("REPL[2]"), :Main_1a042b14)::Any ││╻╷ invokelatest
└─── goto #5 │││┃ #invokelatest#2
5 ── goto #6 │││
6 ── goto #27 if not %14 ││
7 ── nothing::Nothing │
8 ── nothing::Nothing
Which is a invokelatest.
We currently don't offer the user to enter that call, but we should be able to.
Advanced: dump [P]arams cache.
• %9 = invoke current_logger_for_env(::Base.CoreLogging.LogLevel,::Symbol,::Module)::Union{Nothing, Base.CoreLogging.AbstractLogger}
%27 = invoke normpath(::String)::String
%28 = invoke normpath(::String)::String
%29 = invoke normpath(::String)::String
%36 = invoke _replace_(::String,::Tuple{Pair{String, String}},::Int64)::String
↩
Contributor guide
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 from the issue's IR example and the existing “Advanced: dump [P]ams cache” interaction. Trace how the tool exposes listed invoke calls and determine where invokelatest is filtered or omitted; done means the user can enter and inspect this call consistently with the other displayed calls.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100