Garrett Serack
628301be37
* updated files * queue and ready are now separate * checkpoint * found it! fixed missing call * cleaned up and refactored a bit * cleanup * whoops. make sure linter runs! * Make the queue itself static * addressed formatting issues, added more rules to eslint * more formatting, made ready Promise/void * checkpoint * checkpoint * checkpoint * checkpoint (linting) * checkpoint * checkpoint * checkpoint * checkpoint * renamed path to filepath. * checkpoint * checkpoint * so close... * checkpoint again * before making doc * checkpoint * checkpoint * Checkpoint * renamed awaiters * eslint * fix format on generated native strings * add dummy pretest task back in for the moment * change unit test runing * posix calc test failure * make signal dispose better * add est regen script * missed file * checkpoint * Improve scripts a bit * remove hooks for now * remove unused script * remove unused script * filter out files * ensure that eslint works for scripts too * fix build oses to specific version * cleanups and tweaking * adjusted for cosmetic feedback * more * add eslint rule to fix space before/after semicolon * remove tba/tbd * cleanup * Added space-infix-ops rule * cleanup * resolve comments * resolve comments * add simple debug task * spelling fixes * cleanup more * More changes. yay * remove the extra whitespace from before comments * add eslint rule to ensure that there are never extra spaces * adding another eslint rule to ensure that there isn't spacing around unary operators, which we all know is dangerous. Or weird. I forget which * added a space between vs and code because a space is the desired format * removed all mentions of transpiler which was removed * removed an extra comma * removed a trailing slash * removed useless lines * missed as file * reconfigure no-extra-parens rule * added note about yarn install * whatever * more fun * FIx it so that it webpacks correctly * remove refernces to attic * restore line to correct check * fix whitespace * added blank yarn install * removed
C/C++ for Visual Studio Code
Repository | Issues | Documentation | Code Samples
The C/C++ extension adds language support for C/C++ to Visual Studio Code, including editing (IntelliSense) and debugging features.
Pre-requisites
C++ is a compiled language meaning your program's source code must be translated (compiled) before it can be run on your computer. VS Code is first and foremost an editor, and relies on command-line tools to do much of the development workflow. The C/C++ extension does not include a C++ compiler or debugger. You will need to install these tools or use those already installed on your computer.
- C++ compiler pre-installed
- C++ debugger pre-installed
Here is a list of compilers and architectures per platform officially supported by the extension. These are reflected by the available IntelliSense modes from the extension's IntelliSense configuration. Note that support for other compilers may be limited.
| Platform | Compilers | Architectures |
|---|---|---|
| Windows | MSVC, Clang, GCC | x64, x86, arm64, arm |
| Linux | Clang, GCC | x64, x86, arm64, arm |
| macOS | Clang, GCC | x64, x86, arm64 |
For more information about installing the required tools or setting up the extension, please follow the tutorials below.
Overview and tutorials
C/C++ extension tutorials per compiler and platform
- Microsoft C++ compiler (MSVC) on Windows
- GCC and Mingw-w64 on Windows
- GCC on Windows Subsystem for Linux (WSL)
- GCC on Linux
- Clang on macOS
Quick links
- Editing features (IntelliSense)
- IntelliSense configuration
- Enhanced colorization
- Debugging
- Debug configuration
- Enable logging for IntelliSense or debugging
Questions and feedback
FAQs
Check out the FAQs before filing a question.
Provide feedback
File questions, issues, or feature requests for the extension.
Known issues
If someone has already filed an issue that encompasses your feedback, please leave a 👍 or 👎 reaction on the issue to upvote or downvote it to help us prioritize the issue.
Quick survey
Let us know what you think of the extension by taking the quick survey.
Contribution
Contributions are always welcome. Please see our contributing guide for more details.
Microsoft Open Source Code of Conduct
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.
Data and telemetry
This extension collects usage data and sends it to Microsoft to help improve our products and services. Collection of telemetry is controlled via the same setting provided by Visual Studio Code: "telemetry.enableTelemetry". Read our privacy statement to learn more.