Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Add output parser for include-what-you-use#4548

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
malsyned wants to merge2 commits intomicrosoft:main
base:main
Choose a base branch
Loading
frommalsyned:iwyu-parser

Conversation

@malsyned
Copy link
Contributor

@malsynedmalsyned commentedAug 14, 2025
edited
Loading

image

This changes visible behavior & documentation

The following changes are proposed:

  • Parse include-what-you-use output to generate warning and note diagnostics about missing or superfluous #includes and forward declarations.
  • Addiwyu item to thecmake.enabledOutputParsers option.

The purpose of this change

To add diagnostic messages frominclude-what-you-use to the Problems pane.

Other Notes/Information

include-what-you-use is a C/C++ code linting tool built with LLVM. CMake has built-in integration via theCMAKE_<LANG>_INCLUDE_WHAT_YOU_USE variable and<LANG>_INCLUDE_WHAT_YOU_USE property.

I didn't addiwyu to the default value ofcmake.enabledOutputParsers but I don't think there is any harm in doing so. Its diagnostic messages are quite distinctive and unlike those of the already-supported compilers and linkers. I'd be very open to modifying this PR to make it a default.

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

No reviews

Assignees

@hanniavalerahanniavalera

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@malsyned@hanniavalera

[8]ページ先頭

©2009-2025 Movatter.jp