René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Lazily Evaluate Variables/threads/stacktrace for better stepping performance","articleBody":"https://github.com/PowerShell/PowerShellEditorServices/blob/bbf627b597011a8c43379abe025d60df15449087/src/PowerShellEditorServices/Services/DebugAdapter/DebugService.cs#L985-L986\r\n\r\nThis line \"blocks\" stepping for about half a second, and I don't currently see any reason why it has to. We should return to the user as fast as possible that we have reached our breakpoint, and do this heavy processing at the point the DAP makes the `stackTrace`, `scopes`, and `variables` requests, because those are non-blocking to the UI\r\n\r\nEDIT: Based on DAP testing, currently after a stop, vscode requests `threads` and `stacktrace` before the UI updates with the new breakpoint, but I think if we implement `supportsDelayedStackTraceLoading` capabilities, we can quickly return a first stack trace, and since threads is basically a dummy since we don't currently support multi-thread stacktraces, we can probably make some responsiveness improvements here.\r\n","author":{"url":"https://github.com/JustinGrote","@type":"Person","name":"JustinGrote"},"datePublished":"2024-10-11T04:53:07.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":9},"url":"https://github.com/2189/PowerShellEditorServices/issues/2189"}