With the introduction of debugging tools, software developers were empowered to interactively investigate the control flow of software programs to find bugs in live environments. At JetBrains, we've a
The code is already compiled. what do you mean it’s preemptively compiled? If you’re talking about executed, they explicitly called that out…
A prediction can also end at a function call the debugger is cautious about evaluating. That is for your own (or your software’s) well-being. Since code is executed during debugging, the debugger has to be sure that it’s not causing any mutations. When running the above example, we must confirm the evaluation of the int.TryParse method (more about that later):
As mentioned in the previous section, the predictive debugger won’t evaluate possibly impure functions to avoid side effects. As a human developer, you most certainly have more knowledge about the code, which is why we give you the possibility to forcefully evaluate a call by clicking the hint:
I mean that in running it, it is by basic definition compiling what it is running into machine language. So no, code is most certainly not already compiled into machine language as I’m writing or reviewing it.
By necessity, when you’re in the debugger your code has already been compiled either way, no? Or am I missing something here?
This isn’t executing your code as you’re writing it (though it does support Edit & Continue), this is preemptively executing the next lines in your code when you’re already paused in the debugger - which means it’s been compiled and already running.
you’re misunderstanding. this is a function of the debugger. Your code has already been compiled and is currently running if you are using this feature.
The code is already compiled. what do you mean it’s preemptively compiled? If you’re talking about executed, they explicitly called that out…
I mean that in running it, it is by basic definition compiling what it is running into machine language. So no, code is most certainly not already compiled into machine language as I’m writing or reviewing it.
You question doesn’t make much sense to me.
By necessity, when you’re in the debugger your code has already been compiled either way, no? Or am I missing something here?
This isn’t executing your code as you’re writing it (though it does support Edit & Continue), this is preemptively executing the next lines in your code when you’re already paused in the debugger - which means it’s been compiled and already running.
you’re misunderstanding. this is a function of the debugger. Your code has already been compiled and is currently running if you are using this feature.
Ah, you’re right, that does make more sense. So this runs while the program is in debug mode.
That relieves me a bit. I just feel like a lot of these new IDE features are things that no one specifically asked for.