After some testing on Windows with the current lldb-dap, i.e without the PseudoConsole, lldb-dap I think that lldb-dap is very much usable. I was able to step through a simple C++ program in VSCode, print variable values, the backtrace etc.
However, I don’t get any output from the program:
macOS
Windows
Using the PseudoConsole will allow us to get the program’s STDOUT (and STDIN) from lldb-dap, just like on POSIX platforms.
In parallel, I was able to dynamically load the CreatePseudoConsoleAPI which is needed for this update. This means we can still have an executable which runs on Vista/7/8 and also on Windows 10/11, but with the PseudoConsole enabled on these versions.
Given that, I think we don’t need to bump the Windows version, because despite missing the program output, lldb-dap is still usable on Windows without the PseudoConsole (stepping, stacktrace, variable printing work), and lldb can print the output of the program when running from the CLI.