"Cout is ambigous" error

[aadia1234]

          Hi, I'm experiencing this exact issue for the first time (June 2023). Here is what I see:

It seems that whenever I'm creating a new statement or modifiyng one of my previous print statements the error occurs. It goes away if I comment then uncomment #include<iostream> or restart vscode (but reappears soon after)

Specs:
Apple M1 Pro
macOS: 13.3.1 (a) (22E772610a)

VSCode:

Version: 1.79.2
Commit: 695af097c7bd098fbf017ce3ac85e09bbc5dda06
Date: 2023-06-14T08:58:33.551Z
Electron: 22.5.7
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: 10.8.168.25-electron.0
OS: Darwin arm64 22.4.0

C/C++ tool version: v1.16.2

Originally posted by @gam3boy1 in #9471 (comment)

[ranganpal]

I am also getting same error today

[TashinParvez]

I am also getting same error

[bobbrow]

I'm not currently reproducing the error on Windows. Can someone run the C/C++: Log Diagnostics command and share it with us? So far, I see one user reporting it happening on Apple M1 Pro. Is anyone seeing this on Windows or linux?

[aadia1234]

I'm not currently reproducing the error on Windows. Can someone run the C/C++: Log Diagnostics command and share it with us? So far, I see one user reporting it happening on Apple M1 Pro. Is anyone seeing this on Windows or linux?

Here's a link to a recent post with the exact same issue on windows: #11123

[aadia1234]

@bobbrow I'd like to point out that the label "regression" doesn't fit because this problem has occurred in vs code previously: #9471 (comment)

[sean-mcmanus]

@gam3boy1 This new issue does appear to be a 1.16.2 regression, since #9471 has different repro steps.

[sean-mcmanus]

We've repro'd the issue -- the recommended workaround is to downgrade to 1.15.4.

A 100% repro requires making an edit inside the function and moving the cursor to a new line (although it's possible a repro is still possible randomly without an edit).

[michelleangela]

This is now fixed in release version 1.16.3.