Skip to content

ABI/API checker: always print fully qualified names for types when diagnosing module difference #26873

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

Conversation

nkcsgexi
Copy link
Contributor

This change introduces a Json format change where we always print fully
qualified type names everywhere. This is beneficial for diagnosing purposes but
may not be ideal for generating migrator scripts. To resolve this conflict, the
patch also introduces a flag -migrator to opt-out fully qualified type names.

After the format change, we need to update the ABI and API baselines for the
Swift stdlib.

…agnosing module difference

This change introduces a Json format change where we always print fully
qualified type names everywhere. This is beneficial for diagnosing purposes but
may not be ideal for generating migrator scripts. To resolve this conflict, the
patch also introduces a flag -migrator to opt-out fully qualified type names.

After the format change, we need to update the ABI and API baselines for the
Swift stdlib.
@nkcsgexi
Copy link
Contributor Author

@swift-ci please smoke test

@nkcsgexi
Copy link
Contributor Author

To make this format change fly without introducing a lot of false positives, I have to update the ABI/API baseline for the stdlib with the commit. However, the baseline is still generated from master instead of 5.1 branch. I plan to have a separate commit to fix rdar://54653088

cc: @stephentyrone and @lorentey

@nkcsgexi nkcsgexi merged commit 25b849b into swiftlang:master Aug 27, 2019
@nkcsgexi nkcsgexi deleted the api-digester-fully-qulified-type-everywhere branch August 27, 2019 20:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant