Skip to content

Miscellaneous cleanup and consolidation for implementation-only checking #23972

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

jrose-apple
Copy link
Contributor

  • Adjust the implementation-only diagnostics to sound more similar
  • Don't bother checking implementation-only import use for accessors
  • Consolidate names of implementation-only checking functions as "exportability"

John and I had slightly different styles when adding these; better
to keep them in harmony.
Their associated AbstractStorageDecl is already being checked, and
will produce a better error.
Another place where John and I used different terms.
@jrose-apple
Copy link
Contributor Author

@swift-ci Please smoke test

@jrose-apple
Copy link
Contributor Author

That second one's actually semantics-changing, but it's also the simplest diff.

@jrose-apple
Copy link
Contributor Author

@swift-ci Please smoke test Linux

1 similar comment
@jrose-apple
Copy link
Contributor Author

@swift-ci Please smoke test Linux

@jrose-apple jrose-apple merged commit d4a5740 into swiftlang:master Apr 12, 2019
@jrose-apple jrose-apple deleted the implementation-only-implementation---only branch April 12, 2019 20:19
jrose-apple added a commit to jrose-apple/swift that referenced this pull request Apr 19, 2019
…ly-implementation---only

Miscellaneous cleanup and consolidation for implementation-only checking

(cherry picked from commit d4a5740)
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.

3 participants