Skip to content

[docs] Clarify wording around adding new associatedtypes to protocols. #33696

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

varungandhi-apple
Copy link
Contributor

@varungandhi-apple varungandhi-apple commented Aug 29, 2020

cc Xi: I don't know if the API/ABI checkers already account for this, we might want to update them if they don't already do that.

availability), as long as it has a default implementation.
availability), as long as it has a default implementation. If the protocol
did not have one or more ``associatedtype`` requirements before the change,
then this is a `binary-compatible source-breaking change`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should these be double-backticks?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

@nkcsgexi nkcsgexi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's great to document this!👍

@varungandhi-apple
Copy link
Contributor Author

@swift-ci please smoke test and merge

@swift-ci swift-ci merged commit c708785 into swiftlang:master Aug 31, 2020
@varungandhi-apple varungandhi-apple deleted the vg-fix-doc-library-evolution-protocols branch August 31, 2020 23:51
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.

4 participants