JuliaDebug / JuliaDebug/Cthulhu.jl
highlight non-constant globals
Open
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 709
- Forks
- 46
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 2
Description
Right now, there's no way to tell if an access to a GlobalRef that's not its own statement references a constant or an untyped global. Maybe we can add some highlighting here to avoid confusion as in https://github.com/JuliaLang/julia/issues/43470#issuecomment-997278696.
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 by reproducing the highlighting behavior for a GlobalRef used outside its own statement and compare constant versus untyped-global accesses. Use the linked Julia issue comment as the expected behavior reference; done means the two cases are visually distinguishable without changing existing highlighting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100