> On Nov 11, 2016, at 1:53 PM, Hooman Mehr via swift-evolution > <[email protected]> wrote: > > +1. > > This is the best we can do for now, given time and resources.
Agree. There will still be frustrating limitations at times, but this is a huge step forward. > >> On Nov 9, 2016, at 4:03 PM, Joe Groff via swift-evolution >> <[email protected] <mailto:[email protected]>> wrote: >> >> During the first round of review for SE-0143, there was concern about the >> clarity of the proposal as written, since the discussion fixated on a number >> of ancillary issues not intended to be core to the proposal. Doug has >> revised the proposal for another round of feedback, so the review period for >> this proposal has been extended through November 15. >> >> -Joe >> >>> On Sep 28, 2016, at 3:15 PM, Joe Groff via swift-evolution >>> <[email protected] <mailto:[email protected]>> wrote: >>> >>> Hello Swift community, >>> >>> The review of “Conditional Conformances” begins now and runs through >>> October 7. The proposal is available here: >>> >>> >>> https://github.com/apple/swift-evolution/blob/master/proposals/0143-conditional-conformances.md >>> >>> <https://github.com/apple/swift-evolution/blob/master/proposals/0143-conditional-conformances.md> >>> Reviews are an important part of the Swift evolution process. All reviews >>> should be sent to the swift-evolution mailing list at >>> >>> https://lists.swift.org/mailman/listinfo/swift-evolution >>> <https://lists.swift.org/mailman/listinfo/swift-evolution> >>> or, if you would like to keep your feedback private, directly to the review >>> manager. When replying, please try to keep the proposal link at the top of >>> the message: >>> >>> Proposal link: >>> >>> https://github.com/apple/swift-evolution/blob/master/proposals/0143-conditional-conformances.md >>> >>> <https://github.com/apple/swift-evolution/blob/master/proposals/0143-conditional-conformances.md> >>> Reply text >>> >>> Other replies >>> >>> What goes into a review? >>> >>> The goal of the review process is to improve the proposal under review >>> through constructive criticism and, eventually, determine the direction of >>> Swift. When writing your review, here are some questions you might want to >>> answer in your review: >>> >>> What is your evaluation of the proposal? >>> Is the problem being addressed significant enough to warrant a change to >>> Swift? >>> Does this proposal fit well with the feel and direction of Swift? >>> If you have used other languages or libraries with a similar feature, how >>> do you feel that this proposal compares to those? >>> How much effort did you put into your review? A glance, a quick reading, or >>> an in-depth study? >>> More information about the Swift evolution process is available at >>> >>> https://github.com/apple/swift-evolution/blob/master/process.md >>> <https://github.com/apple/swift-evolution/blob/master/process.md> >>> Thank you, >>> >>> -Joe >>> >>> Review Manager >>> >>> _______________________________________________ >>> swift-evolution mailing list >>> [email protected] <mailto:[email protected]> >>> https://lists.swift.org/mailman/listinfo/swift-evolution >>> <https://lists.swift.org/mailman/listinfo/swift-evolution> >> >> _______________________________________________ >> swift-evolution mailing list >> [email protected] <mailto:[email protected]> >> https://lists.swift.org/mailman/listinfo/swift-evolution > > _______________________________________________ > swift-evolution mailing list > [email protected] > https://lists.swift.org/mailman/listinfo/swift-evolution
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
