Skip to content

Resilient re-ordering of associated types #15806

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

Merged
merged 3 commits into from
Apr 6, 2018

Conversation

slavapestov
Copy link
Contributor

No description provided.

@slavapestov
Copy link
Contributor Author

@DougGregor Maybe this is a bad idea, but the cleanup and evolution tests are still valid. :)

@slavapestov slavapestov requested a review from DougGregor April 6, 2018 22:42
@slavapestov
Copy link
Contributor Author

@swift-ci Please smoke test

@slavapestov slavapestov closed this Apr 6, 2018
@slavapestov slavapestov reopened this Apr 6, 2018
@slavapestov
Copy link
Contributor Author

@swift-ci Please smoke test

@slavapestov slavapestov merged commit 17fd8af into swiftlang:master Apr 6, 2018
@DougGregor
Copy link
Member

Sorting associated types is a good step... I'm still debating (with myself) whether we should go all the way to indirecting associated types so we can resiliently add defaulted ones later.

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.

2 participants