-
Notifications
You must be signed in to change notification settings - Fork 15
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support multiple versions of clang-format
#10
Comments
Sure!
I guess it would have to be be multiple rules? |
Haven't forgot about this. Just need to find IRL time to get on with it :)
Yeah, something along those lines. We would likely need to change the Python entry point to accept the requested LLVM version. So
Would make sense. LLVM tooling has subtle difference between each version so changing that hook would be a break for downstream users. It might make sense to lock that hook to LLVM 11 (which it is now) to not break downstream users and encourage downstream users to decide on a |
FWIW the place I'm downloading from -- Chrome's repository of tools -- doesn't track LLVM releases, but rather just has random hashes that are updated...whenever they feel like it. You could try downloading from the LLVM website, I guess, and then maybe you could do based on LLVM releases. |
@jlebar I have submitted a MR to support multiple versions. Please review. |
Would the project be open to supporting specifying which version of
clang-format
to download?The upstream S3 has multiple versions of
clang-format
.Would there be interest in supporting a
--clang-version
type argument that determines which SHA to lookup.Happy to look into a patch along these lines.
The text was updated successfully, but these errors were encountered: