maulingmonkey / template_rust_vscode

A thorough demo of everything you might want to configure for rust development in VS Code.

What even is this?

A thorough demo of everything you might want to configure for rust development in VS Code, along with a small hello world style program to test it out on.

Possible usage

git clone https://github.com/MaulingMonkey/template_rust_vscode.git
cargo new NEW_PROJECT --bin
robocopy template_rust_vscode\.vscode NEW_PROJECT\.vscode *.*
robocopy template_rust_vscode         NEW_PROJECT         Setup.md

• Setup everything
• Replace ${workspaceFolderBasename} throughout .vscode\launch.json with your new Cargo.toml package.name, so you can rename the folder locally.
• Cull unused stuff from Setup.md

template_rust_vscode's Issues

New project script?

Might be worth writing a new_project.cmd script that can be dropped into your %PATH% to create a new project from the template per the current readme instructions.

*-pc-windows-gnu: Cannot use an internal console

launch.json sets "externalConsole": true to workaround this issue - allowing it to be false causes NullReferenceException s and kills the debugging session. Presumably a bug in ms-vscode.cpptools ?

*-pc-windows-gnu: Doesn't use rust-gdb wrapper / rust pretty printers

rust-gdb adds rust specific pretty printers - these could be manually configured in lieu of using rust-gdb.

launch.json: Schema warning spam ("program" and "cwd" not set)

Windows specific builds intentionally don't set a fallback "program" or "cwd" on non-windows platforms. This causes warnings.

*-pc-windows-gnu: MSYS2 GDB can't pause or add breakpoints while unpaused

While you can hit initially set breakpoints in GNU builds, vs code can't seem to set breakpoints while executing, nor pause execution, via the MSYS2 GDB. I'm guessing this has something to do with the MI interface or is just a GDB bug on windows, since VS code can pause WSL binaries just fine.

settings.json: Schema warning spam (tasks match multiple schemas?)

Several tasks match multiple schemas. Don't know why - maybe they're too terse?