>Atom died for this
Atom died for this
Works on my machine.
>using namespace std;
cringe & yikes pilled
Happy?
You probably need to install a plugin
>no spacing
>shit style
>using namespace std;
when will you get a job, user?
????
why are you using visual studio? do you still need an adult to hold your hand when you cross the road? write your own damn code and stop relying on intellisense
std::endl dummy
>reload required
every time you see something stupid beyond belief remember the majority of this board consists of pajeets. Everything will make sense now.
????
What theme?
Abyss
maam I repeat do not redeem the atom
do not redeeem stupid basterd bich
>cout
op be retarded
it's "count" with n lmao you dyslecix
what does your code smell like?
cum
>a thread died for this
OP, just fucking reinstall windows in a blank state.
support.microsoft.com
And just follow the vscode tutorial on msdn step by step, don't use the same code, don't use the same cmake file, use exactly the same stuff.
Other than that, you could technically set this value in cmake:
CMAKE_EXPORT_COMPILE_COMMANDS
and show us the values in compile_commands.json (in the build directory, after you configured cmake).
It's also possible to try out clangd (which actually depends on compile_commands.json), but it's more jankier, since intellisense is supposed to "just work" tm, because it just scans all the source code in the directory and applies the language server to it, while clangd is less magical (clangd also very annoying if you want a setup where you have multiple build directories).
Good morning sir there is no way to fix your issue just delete each and everything and start over from scratch please sir