JuliaDebug / JuliaDebug/Debugger.jl
Macro for non-interactive 'compiled mode'
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 514
- Forks
- 50
- Avg merge
- 9d 9h
- Merged PRs (30d)
- 1
Description
Would it be possible to add macros to activate/deactivate 'compiled mode' in a similar way to the breakpoint macro @bp?
For example, if I have a program that has a lot of initialization, which takes a very long time in the interpreter, I think it would be nice to be able to do something like
function main()
@enter_compiled_mode
<A bunch of calls to expensive initialization functions>
@exit_compiled_mode
# Now we can run in the interpreter until we hit @bp
<Code that does stuff...>
end
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 locating the existing breakpoint macro @bp and the code paths that control interpreter versus compiled execution. The feature is done when paired macros can activate compiled execution for the initialization section and restore interpreter execution afterward, but the issue names no files or tests to guide verification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100