[aviatesk]

With RecursiveInterpreter, the code passed to Core.eval, also through Base.eval, @eval, and include, is now interpreted in top-level frames linked to the calling frame, instead of being evaluated natively. FrameCode replaces the runtime call in the method of Core.eval with a call to eval_in_frame, which evaluate_eval! handles. Like the compilation of llvmcalls, this is done regardless of optimize, so that debugger commands can step into the evaluation also with optimize=false. Breakpoints, stepping, and exception handling extend into the evaluated code: the calling frame's handlers are passed down (caller_will_catch_err), and interpreted dynamic scopes reach both the evaluation and the lowering of the code. Evaluation starts in the latest world while the calling method keeps its own, and :module expressions go through the native module evaluation of Frame. NonRecursiveInterpreter, or adding the method of Core.eval to compiled_methods, keeps native evaluation.

Top-level frames now follow native world semantics: on Julia 1.12 and later they advance their world only at :latestworld, so a nested eval does not by itself advance the enclosing thunk's world. Thunks start in the latest world, which internally created ones take when they are created, and which Frame(mod, ex) and Frame(mod, src::CodeInfo) now use by default. Selective evaluation must still advance the world at the :latestworld statements it skips, which LoweredCodeUtils does in a coordinated release (xref: JuliaDebug/LoweredCodeUtils.jl#171). A top-level frame with a caller, e.g. from an eval in a method, runs in its own world even when a debugger resumes it with a method at the root; the task world is switched only when it differs, to keep stepping fast.

Related fixes to top-level interpretation:

• A statement that fails to lower throws the error of native evaluation.
• The frame of a nested :thunk is linked to its caller, so breakpoints, errors, and its value propagate (including a :method returned by older lowering).
• A ReturnNode value as a surface statement is not taken for the driver frame's own return.
• get_return of a driver frame returns nothing if its last statement recorded no value, as when an Interpreter overload handles statements.

Stepping with :s inside the evaluated code goes through statements of top-level frames driven by Frame(mod, ex), which builds on the fix of :s for them in #784.

[codecov]

Codecov Report

❌ Patch coverage is 95.18072% with 4 lines in your changes missing coverage. Please review.
✅ Project coverage is 90.86%. Comparing base (ff4d2f8) to head (b8925b8).

Files with missing lines	Patch %	Lines
src/interpret.jl	96.15%	2 Missing ⚠️
src/commands.jl	66.66%	1 Missing ⚠️
src/optimize.jl	90.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #783      +/-   ##
==========================================
+ Coverage   90.83%   90.86%   +0.02%     
==========================================
  Files          12       12              
  Lines        3535     3579      +44     
==========================================
+ Hits         3211     3252      +41     
- Misses        324      327       +3     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.