clangd and clang-tidy initial support #466
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
NikitaNikolaenko
requested review from
benh,
CodingCanuck,
rjhuijsman,
onelxj and
ArthurBandaryk
ArthurBandaryk
approved these changes
Jul 17, 2022
NikitaNikolaenko
force-pushed
the
folming.clangd
branch
6 times, most recently
from
a7e11e9 to
6423309
Compare
Aviator status
This PR was merged using Aviator. |
NikitaNikolaenko
force-pushed
the
folming.clangd
branch
from
6423309 to
0439358
Compare
aviator-app
bot
force-pushed
the
folming.clangd
branch
from
0439358 to
15d6888
Compare
|
Branch up-to-date, waiting for checks. |
1 similar comment
|
Branch up-to-date, waiting for checks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allows clangd LSP to work in VS Code (or any other IDE/Code Editor that has some kind of a support for clangd).
The output of the added rule can also be used in clang-tidy (which is how #465 PR was created).
The README in https://github.com/hedronvision/bazel-compile-commands-extractor was especially helpful in the process of setting everything up.