11–20 of 42 posts
It is funny how long this has been an issue and how I and so many people have given up stepping in and instead jump to the actual user function, set break point, and then step over at the source location, then unset the breakpoint and continue. A bunch of crazy steps which you end up doing again and again. Needless to say, this improvement is much welcomed!
As a developer spending hours a day in Visual Studio with C++ as primary language this is a major improvement in terms of development time. Debugging is a a time consuming task in any language, but library headers from STD and Boost slow down the process tremendously.
Although it does help, I would say its only a bit faster than actually just setting a breakpoint of where you want the code to stop, and running till then, unlike Microsoft's example which shows 85 step intos, as if people actually do that.
Great. Now if they can actually fix the debugger to lock onto a single thread when stepping thru multithreaded code. Currently when you set a breakpoint and step, you’ll be jarringly switched back to the breakpoint when another thread hits it. The solutions now are tedious : https://visualstudio.uservoice.com/forums/121579-visual-stud...
Just a clarifying note : this is the closed Visual Studio, and not free software - VS Code - which usually does the rounds on HN. I'm far more excited about the LSP protocol for C++ which would bring like this to all IDEs.
Why has it taken this long for something so obvious to be implemented?
I love this idea. I wonder if something similar could be ported/achieved for JavaScript!