New flag -Ycc-no-emit for stripping CC annotations from emitted TASTy
#23671
Conversation
This file contains hidden or 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
natsukagami
force-pushed
the
cc-no-tasty-emit
branch
from
e554ca5 to
a3e86ac
Compare
Member
|
@natsukagami should we kill this PR now or do you want to keep it open? |
Contributor
Author
|
I still have use for the code, but I think we can axe the PR |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
New flag
-Ycc-no-tastydrops capture checking annotations from TASTy.Note that the following are not stripped, since they are not annotations:
However stripping them would break API compatibility, and presumably (in the latter case) binary compatibility compared to the annotated version.