Skip to content

Conversation

@amartini51
Copy link
Member

No description provided.

@amartini51 amartini51 changed the title SE-0140 has been implemented SE-0140 and SE-110 been implemented Sep 23, 2016
@amartini51 amartini51 changed the title SE-0140 and SE-110 been implemented SE-0140 and SE-110 have been implemented Sep 23, 2016
@amartini51 amartini51 changed the title SE-0140 and SE-110 have been implemented SE-0140 and SE-0110 have been implemented Sep 23, 2016
@amartini51 amartini51 merged commit 43b625c into swiftlang:master Sep 23, 2016
@DougGregor
Copy link
Member

Are you going to update index.xml as well?

@amartini51
Copy link
Member Author

Fixed index.xml in 1b8345c, thanks.

@DougGregor
Copy link
Member

Wait, SE-0110 didn't actually get implemented in Swift 3. Part of it went it, but got reverted here:

swiftlang/swift@f42158b

@amartini51
Copy link
Member Author

amartini51 commented Sep 23, 2016

Looks like our tracking bugs are wrong then: Jira and Radar (rdar://27383557) say this landed. Good thing this got called to our attention!

@benrimmington
Copy link
Contributor

@DougGregor swiftlang/swift@f42158b is swiftlang/swift#3922, which only reverts swiftlang/swift#3895 (the first attempt of SE-0110).

swiftlang/swift#4102 (the second attempt) has not been reverted. It isn't in the swift-3.0-branch, so the current status should be Implemented (Swift 3.1).

Would it be better to wait until Swift 4, either by reverting swiftlang/swift#4102, or by using the -swift-version flag of swiftlang/swift#4826?

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