Shuhei Kadowaki
Shuhei Kadowaki
Supposed to work with https://github.com/JuliaLang/julia/tree/avi/bestguess-overload.
For `statementnumbers` to function in v1.12, there's a need for a tool that can rebuild the full `codelocs` object from `Core.DebugInfo`, similar to what we could do just by looking...
https://github.com/JuliaDebug/JuliaInterpreter.jl/blob/ebc743a99ec681a22e3cd0ff3676fc2399f79601/src/utils.jl#L280-L285 I don't understand this commit -- do we now store some macro expansion context within `debuginfo`? _Originally posted by @aviatesk in https://github.com/JuliaDebug/JuliaInterpreter.jl/pull/606#discussion_r1537492588_
It looks like this "optimization" introduces a very bad interaction with the new lineinfo format: https://github.com/JuliaDebug/JuliaInterpreter.jl/blob/28dd37ce0f7bcb357bfb820b1d6b53b98aa3796c/src/optimize.jl#L76-L92 ```julia julia> using JuliaInterpreter julia> fnone1() = nothing; julia> let m = only(methods(fnone1)) JuliaInterpreter.FrameCode(m,...
This test case is broken on `≥v"1.11-"`. https://github.com/JuliaDebug/JuliaInterpreter.jl/blob/eae07f9c6f8155f2d1edb7638834856da732f466/test/debug.jl#L431 We need to revisit the implementation of `maybe_step_through_kwprep!` https://github.com/JuliaDebug/JuliaInterpreter.jl/blob/eae07f9c6f8155f2d1edb7638834856da732f466/src/commands.jl#L273-L278 _Originally posted by @aviatesk in https://github.com/JuliaDebug/JuliaInterpreter.jl/pull/615#discussion_r1533547783_
/cc @vtjnash
Still needs to adjust to https://github.com/JuliaLang/julia/pull/52415.
After #52169, there is no need to taint `:consistent`-cy on accessing undefined `isbitstype` field since the value of the fields is consistent always.
After experimenting with #49235, I started to question if we are getting any actual benefit from the `throw` block deoptimization anymore. This commit removes the deoptimization from the system entirely....