AbbreviatedStackTraces.jl
AbbreviatedStackTraces.jl copied to clipboard
BioTurboNick
For example, when broadcasting I get these kinds of messages clogging the stacktrace: ```julia-repl [7] _broadcast_getindex_evalf @ Main.Wrangling ./broadcast.jl:709 [inlined] [8] _broadcast_getindex @ Main.Wrangling ./broadcast.jl:682 [inlined] [9] getindex @ Main.Wrangling...
Relies on Base.display_error instead.
If a package contains a nested module, the public types of that module should not be considered public to the parent module unless the parent module itself re-exports them, or...
Currently AbbreviatedStackTraces doesn't work in VSCode if you have `using AbbreviatedStackTraces` in your startup.jl file. If you try to `using` again after startup, it still doesn't work. However it does...
See: https://github.com/JuliaLang/julia/pull/41099
Consider trimming top-level frames when an error is encountered when `using` a package. To reproduce, just add an undefined variable name inside a module then trigger precompilation via `using`. ```...
Inlined methods and some others don't carry module information with them, so they show up as "Unknown" when abbreviated. May want to look into how that could be corrected so...
Brainstorm: What if MethodErrors from "internal" frames (in the sense I'm using for AbbreviatedStackTraces) were shown differently? May not belong in this package but I'll document it here anyway. A...
Currently, workers show all stack frames even if launched at the REPL. It might be better to abbreviate them, too, so long as it only happens when launched from the...