microsoft / microsoft/vscode-cpptools
Show problems for warnings (e.g. when warnings as errors is enabled)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
Using MinGW/Cygwin, what is the closest I can come to get the extension highlight all the warnings errors from these flags? -Wall -Wextra -pedantic -Wconversion -Werror.
https://github.com/Microsoft/vscode-cpptools/issues/2091 is relevant, but it doesn't answer if its possible to enable these warnings on MinGW/Cygwin gcc/g++ if it's possible at all. I'm sorry if this is a duplicate, thanks in advance.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported MinGW/Cygwin behavior with gcc or g++ and the flags -Wall, -Wextra, -pedantic, -Wconversion, and -Werror. Compare the result with issue #2091 and determine the extension entry point or configuration responsible for warning diagnostics; done means supported warnings are highlighted as problems or the limitation is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- compilers, devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100