Skip to content

Replace the deprecated CountableRange with Range #1542

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 1 commit into from
Mar 22, 2018

Conversation

hartbit
Copy link
Contributor

@hartbit hartbit commented Mar 22, 2018

No description provided.

@hartbit hartbit requested a review from aciidgh March 22, 2018 20:20
@hartbit
Copy link
Contributor Author

hartbit commented Mar 22, 2018

@swift-ci please smoke test

@aciidgh
Copy link
Contributor

aciidgh commented Mar 22, 2018

We need to maintain compatibility with Swift 4.0 in Basic and Utility

@hartbit hartbit force-pushed the countablerange-warning branch from 5328798 to bc54cdf Compare March 22, 2018 20:41
@hartbit
Copy link
Contributor Author

hartbit commented Mar 22, 2018

@aciidb0mb3r I added swift version checks

public typealias Indices = CountableRange<Int>
#endif
Copy link
Contributor

Choose a reason for hiding this comment

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

@jrose-apple is this check enough to not break compatibility with 4.0?

Copy link
Contributor

@jrose-apple jrose-apple Mar 22, 2018

Choose a reason for hiding this comment

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

Should be fine, but shouldn't that be checking for 4.1, not 4.2? Yes, should be fine.

@hartbit
Copy link
Contributor Author

hartbit commented Mar 22, 2018

@swift-ci please smoke test

@hartbit hartbit merged commit b66765f into swiftlang:master Mar 22, 2018
@hartbit hartbit deleted the countablerange-warning branch December 3, 2018 18:07
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