Move instruction pointer while debugging

[gottfired]

Describe the solution you'd like
It would be great, if you could move the instruction pointer during debugging like in other languages/IDEs

Additional context
This is possible e.g. with C++ in Visual Studio or Swift in XCode

[suzmue]

Hi @gottfired! Could you provide some more details about what you would like to see? How do these other languages allow moving the instruction pointer?

[gottfired]

In Xcode and Visual Studio (not Visual Studio Code) you can drag the instruction pointer (ie. the arrow indicating you current point of execution) to a new position.

This simply sets the point where program flow will continue execution, so basically the next ASM instruction. When you drag back it does not roll back any changed data or other side effects. But in many cases this is quite useful, e.g. when debugging an algorithm and you want to rerun a loop you can simply have a breakpoint after a loop and drag back to the beginning, or if you accidentally skip going into a function you can drag back to the point before. In the screen shot above I could e.g. drag directly to the assert, skipping the two lines in between. Or I could put a breakpoint at the assert and drag back to the start of the function.

[hyangah]

For UI/UX, DAP has supportsGotoTargetsRequest
but this is more about Delve's capability and Go's runtime support if needed.

go-delve/delve#1045 discusses this topic in the delve project.

@aarzilli's initial assessment go-delve/delve#1045 (comment) was written in 2017, and Go's compiler/runtime had been changed a lot since then. So I don't know if how many more or less constraints were added to the list.

[suzmue]

Closing this as there is not support in Delve and the Go runtime, so there is nothing for the extension to do.