JuliaDebug / JuliaDebug/CodeTracking.jl
Revise should track macro-created functions defined in the REPL
Open
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 150
- Forks
- 11
- Avg merge
- 22m
- Merged PRs (30d)
- 1
Description
macro makefn(name)
name = Symbol(name)
quote
$(esc(name))() = print("hello")
end
end
julia> @makefn f
f (generic function with 1 method)
julia> f()
hello
julia> @code_string f()
" \$(esc(name))() = println(\"hello\")"
In an ideal world, @code_string f() would return something like f() = println(\"hello\")".
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 reproducing the macro and @code_string f() example in the Julia REPL, then inspect how CodeTracking handles functions created by macros there. Done means the existing example reports the generated function definition, such as f() = println("hello"), instead of the macro source.
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
- 35/100