Open tpkowastaken opened 2 years ago
Thanks for reporting this. I've reproed the issue. It doesn't repro with VS. It could be some difference in how we're updating IntelliSense after an edit.
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
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
same bug, VSCode vision:1.79.2, GCC vision:10.3.0, the code can run well but the terminal remind me that "Cout is ambigous".
i am also experiencing same bug issue on the latest release (may 2023) version-1.79.2 and it was even afer the update of latest release.
Yeah, Im also facing the same bug, as of 23 June 2023
Why does this appear ? how is cout/cin amigious ?? How to fix this ??
Same bug appeared
FYI, this issue doesn't seem related to the new issue with 1.16.2, because this issue requires very particular edits.
We're tracking the new/regression issue with https://github.com/microsoft/vscode-cpptools/issues/11122 .
I have the same error, apparently the solution is to install the extension pack. Good to me it worked. This one is without the extension pack
With extension pack
@tpkowastaken Installing the extension pack is not expected to change the behavior (the bug might repro after making an edit in main). We plan to release a fix in 1.16.3 in the next hour or so.
I reinstalled the C/C++ Extension after v1.16.3 released, the bug is fixed now You can see, no problems are detected
Yes, the new 1.16.2 issue is fixed with 1.16.3 (but FYI the original issue is a different bug that still exists, but is harder to repro).
I have the same error, apparently the solution is to install the extension pack. Good to me it worked. This one is without the extension pack
With extension pack
Thanks it worked when i reloaded the Extension Pack
I have similar error, not with std::cout and in proprietary code, so for obvious reasons I can't show a screenshot with an error message that a variable defined few lines above in the same anonymous namespace is ambiguous. Problem appears, disappears and appears again. Despite reported ambiguity, Ctrl+click works, going to the definition, so wild guess is classifying reparsed type definition as new, while should match with already known to the engine. C/C++ extension 1.19.9
@jakublATopera 1.19.9 has a bug in which missing include errors won't be shown if C_Cpp.errorSquiggles is set to "enabled" (https://github.com/microsoft/vscode-cpptools/issues/12134) -- if you change that setting to the default value you may see the cause of the cause is a header that isn't being found. Also, it might be worth seeing if the repro still occurs with 1.18.5.
Hi! I seem to be having a similar issue for the first time as of 05/15/2024. I'm being told that cin is ambiguous, but cout is fine.
C/C++ extension version 1.20.5
Included headers are:
#include <iostream>
#include <string>
#include <fstream>
#include <regex>
#include <vector>
#include <map>
#include <cctype>
using namespace std;
Having this problem as well
Environment
Bug Summary and Steps to Reproduce
"Cout is ambigous" error when using namespace std
when programming in c++ while there is a code including this:
then there is a chance that there appears to be "cout is ambigous error" in problems tab even though there is no error to be found whatsoever. It appears for every "cout" in the file. if you write std:: before the cout the error gets removed.
Steps to reproduce:
Note: if you restart vs code or wait long enough (4minutes) and then edit - it mostly disapears.
Other Extensions
I have tested this with only c++ extension v1.10.7 running and C++ extension pack v1.2.0 running.
Additional Information
I have faced this issue on a low-tier laptop which might be a bit slower than usual. Make sure to replicate on lower-end hardware
My specs: CPU: Intel(R) Core(TM) i7-4702MQ CPU @ 2.20GHz Memory: 16GB
A screenshot of this happening: