I recently tried using VSCode debugger to “step into” a function from an external package, but VSCode pointed me to a strange code location. Eventually I figured out that the function was not written out, but was generated by a macro in the package involving eval calls.
Would it be possible for future versions of the VSCode extension to show the generated function body and allow the user to step through the lines when debugging?