GDB pretty printing not enabled by default in VSCode when using `ms-vscode.cpptools` debugger

When trying to debug in VSCode on Ubuntu with GNU gdb (Ubuntu 16.2-8ubuntu1) 16.2 I wasn't able to see nice printouts in the variables pane or debug panel.

For example a String just shows the raw underlying Vec

Thanks to this thread:

https://users.rust-lang.org/t/vscode-gdb-rust-analyzer-pretty-printing/73705

I was able to get things working by following OP's tip on including the VSCode settings

{
  "rust-analyzer.debug.engine": "ms-vscode.cpptools",
  "rust-analyzer.debug.engineSettings": {
    "cppdbg": {
      "miDebuggerPath": "${env:HOME}/.cargo/bin/rust-gdb",
      "setupCommands": [
        {
          "description": "Enable pretty-printing for gdb",
          "text": "-enable-pretty-printing",
          "ignoreFailures": false
        }
      ]
    }
  }
}

Could these be enabled by default so everyone can easily see your great GDB integration?

Start by tracing the rust-analyzer.debug.engine and rust-analyzer.debug.engineSettings configuration for the ms-vscode.cpptools debugger. Compare the supplied cppdbg setupCommands with the existing defaults, then check the relevant debugger integration tests if available. Done means Rust debugging enables GDB pretty-printing by default without requiring those user settings.