Update SE-0110's status

[BasThomas]

It was accepted in https://lists.swift.org/pipermail/swift-evolution-announce/2016-July/000215.html

[benrimmington]

@BasThomas, see the comments in PR 726.

Part of SE-0110 was reverted/deferred, due to a usability regression.

Which of the proposal states would be the most accurate?

[BasThomas]

I think "accepted with revisions" might make sense. Otherwise a "partially implemented" status (like you suggested) might be a good alternative. What do you think?

For what it's worth, this came to my attention because of this:

https://twitter.com/slava_pestov/status/983568033422622721

Horray for progress on the final implementation of SE-0110: swiftlang/swift#15843

[benrimmington]

The proposed solution of SE-0110 is available in Swift 4.0.3, so Implemented (Swift 4) might be the best status.

The usability regression examples seem to be more about "tuple splatting" from SE-0029.

[masters3d]

I think deferred is the best status given the supplied link. https://lists.swift.org/pipermail/swift-evolution-announce/2017-June/000386.html

[BasThomas]

Ping @DougGregor — what would be the appropriate status?

[DougGregor]

This proposal is mostly-but-not-completely implemented. I prefer to leave it in the “accepted” state until we are sure it is done, which we hope will be within the next few months