Range-over-func (#61405) statements are going to be compiled into closures passed to the iterator function. I.e. the following code:

for range f {
    body
}

becomes:

f(func() {
    body
})

Delve (and potentially other debuggers) needs a way to correlate the stack frame where the body's closure is executing with the stack frame that it logically belongs to (the "parent" frame), for two reasons:

1. to display variables from the parent frame while the the program is stopped inside the loop's body
2. to make stepping work seamlessly (i.e. step-over from the header line of the loop will move to the first line of the loop's body)

We have discussed during the go team/delve meetings possible solutions for this and the current plan is to keep the closure struct alive and make it accessible through a specially named variable DIE.

This issue is to track this problem (and also for cases where the binary is optimized and a lot of inlining happens to the range-over-func statement).

cc @derekparker @dr2chase