-
Notifications
You must be signed in to change notification settings - Fork 12
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
Add support for exegesis annotator in BHive conversion script #41
Merged
boomanaiden154
merged 11 commits into
google:main
from
boomanaiden154:upstreaming-exegesis-annotator-in-script
Feb 19, 2024
Merged
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
e955393
Add support for exegesis annotator in BHive conversion script
boomanaiden154 21d5023
Merge branch 'main' into upstreaming-exegesis-annotator-in-script
boomanaiden154 31637e8
Address some reviewer feedback
boomanaiden154 7e36f7e
Address reviewer feedback
boomanaiden154 28b3bff
try bumping clang format version
boomanaiden154 4f66e33
Revert "try bumping clang format version"
boomanaiden154 22d22a3
Actually format code
boomanaiden154 79c24c5
Address reviewer feedback
boomanaiden154 07c7ad4
Address reviewer feedback
boomanaiden154 85bb6fd
Merge branch 'main' into upstreaming-exegesis-annotator-in-script
boomanaiden154 e8d8271
Clang-format file
boomanaiden154 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we don't have absl::log?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could, but the rest of the file uses standard library output, so I'm staying consistent with that for now. Not sure what would be preferred though. I think within Google, everything would use
absl::log
, and LLVM has its own output facilities, so this is sort of in no man's land.