VSCode debug with @einsum stops in macro.jl about tullio.jl HOT 5 CLOSED

I still get the same behaviour after installing (and loading) Debugger.

Yes, in a fresh new Julia environment I confirm, that I get the same behaviour after installing (and loading) Debugger.
I filed julia-vscode/julia-vscode#1667

from tullio.jl.

Hi Ralf, thanks for the detailed report! I finally got vscode to co-operate, and can reproduce this.

It's pretty odd, but I don't understand why the macro's let block ought to cause problems. If I define a function f(v,w) = @einsum a[i,j] := v[i] * w[j]; and then call that on line 5, it still stops in the same place; perhaps that means it isn't some weird global scope issue.

from tullio.jl.

Hi Michael, thank you for your efforts.

Now, strange thing:
I installed the package Debugger, https://github.com/JuliaDebug/Debugger.jl, a command line debugger to check if it fails too.
But after installing this package, which is not needed by Julia VSCode, the unexpected behavior of stopping in macro.jl disappears while debugging in VSCode.
Remove this package with rm Debugger and the unexpected behavior in VSCode appears again. I don't know if VSCode debugger has it's own Debugger or JuliaInterpreter or?
Could you imagine, if your time permits, a small macro example which would trigger this behavior of VSCode debugger. Then we could report this to https://github.com/julia-vscode/julia-vscode. In case it is not so simple and takes too much effort, we could also report the current behaviour to julia-vscode.

Cheers

Ralf

from tullio.jl.

I still get the same behaviour after installing (and loading) Debugger. I also don't know the relation between it and the one used by VSCode, they may share some innards.

I think best to open an issue on VSCode, and see what they say. It seems straightforward to reproduce at least the basic version of this, with a registered package. Base.remove_linenums!(@macroexpand1 @einsum a[i,j] := v[i] * w[j]) is not impossibly long to read. Maybe the fix will be obvious to someone there...

from tullio.jl.

Closing this as it looks like it's being tracked, and fixed, elsewhere.

from tullio.jl.