Adding clangd support for metal code
#12
Closed
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
yaroslavyaroslav
force-pushed
the
clangd-metal-support
branch
from
a30f819 to
9c996fa
Compare
yaroslavyaroslav
force-pushed
the
clangd-metal-support
branch
from
9c996fa to
a85cf77
Compare
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.
It's actually the subject.
Provided config helps
clangdto handle metal files correctly and additionally helps it to determine wheremetalsystem libraries to import from.Tested on Sublime Text but should works with VSC as well.
UPD: FWIW this hack does not provide full support of metal, since
clangdcurrently incompatible with metal specific syntax like[[kernel]],constantetc. This leads to significant number of false positives, which may confuse contributor, thus it's not the right feature to be opted-in in repo. So I'm closing this PR so far.