[6.2] ABI checker: drop usage of AllowDeserializingImplementationOnly #82544
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.
6.2 cherry-pick of #82499
Description: AllowDeserializingImplementationOnly was historically added as a defensive
check against deserialization issues introduced by @implementationOnly imports.
It's no longer specified by other tools, thus the ABI checker should drop
it as well.
Origination: A binary module deserialization issue triggered by this legacy option.
Scope of the issue: Fixes potential module deserialization issue during ABI checking
Radar: rdar://153683760.
Risk: Very Low.
Reviewed by: @xymus