Skip to content

SE-0110 Status Deferred #726

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
Jun 22, 2017
Merged

SE-0110 Status Deferred #726

merged 3 commits into from
Jun 22, 2017

Conversation

Coeur
Copy link
Contributor

@Coeur Coeur commented Jun 21, 2017

No description provided.

* Authors: Vladimir S., [Austin Zheng](https://github.com/austinzheng)
* Review Manager: [Chris Lattner](https://github.com/lattner), [Doug Gregor](https://github.com/DougGregor)
* Status: **Implemented (Swift 4 beta)**, **Reverted (Swift 4)**
* Decision Notes: [Implementation Rationale](https://lists.swift.org/pipermail/swift-evolution-announce/2016-July/000215.html), [Reversion Rationale](https://lists.swift.org/pipermail/swift-evolution-announce/2017-June/000386.html)
Copy link
Contributor

Choose a reason for hiding this comment

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

Only a portion of SE-0110 was rolled back in swiftlang/swift#10027 and swiftlang/swift#10414, so you might want to change to:

-* Status: **Implemented (Swift 4 beta)**, **Reverted (Swift 4)**
-* Decision Notes: [Implementation Rationale](https://lists.swift.org/pipermail/swift-evolution-announce/2016-July/000215.html), [Reversion Rationale](https://lists.swift.org/pipermail/swift-evolution-announce/2017-June/000386.html)
+* Status: **Deferred**
+* Decision Notes: [Rationale](https://lists.swift.org/pipermail/swift-evolution-announce/2016-July/000215.html), [Additional Commentary](https://lists.swift.org/pipermail/swift-evolution-announce/2017-June/000386.html)

A status from process.md is required, so that the proposal appears on the status page. I don't know if the status page can handle more than one review manager.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

if only one review manager possible, I suggest we keep the active one (Doug Gregor)

Copy link
Member

Choose a reason for hiding this comment

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

I don't know if the status page can handle more than one review manager.

It can't. Do you think it should?

Copy link
Contributor

Choose a reason for hiding this comment

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

I don't know if the status page can handle more than one review manager.

It can't. Do you think it should?

In this case, I'd keep the original review manager only.

A deferred or rejected proposal will usually have a separate follow-up proposal (with a different review manager).

Would a Partially Implemented status be useful (for SE-0110, SE-0148 and SE-0161)?

@Coeur Coeur changed the title SE-0110 Status Reverted SE-0110 Status Deferred Jun 21, 2017
@benrimmington
Copy link
Contributor

Thanks, @Coeur.

@benrimmington benrimmington merged commit e7f4b9c into swiftlang:master Jun 22, 2017
@Coeur Coeur deleted the patch-1 branch June 22, 2017 04:09
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