[swift-evolution] [swift-evolution-announce] [Review] SE-0143: Conditional Conformances

[T.J. Usiyan]

What is your evaluation of the proposal?
    +1 with concern about the least specialized implementation winning. I
think that this could be tricky to explain or build an intuition around.
Is the problem being addressed significant enough to warrant a change to
Swift?
    Yes
Does this proposal fit well with the feel and direction of Swift?
    Yes
If you have used other languages or libraries with a similar feature, how
do you feel that this proposal compares to those?
    It holds up in general against other systems.
How much effort did you put into your review? A glance, a quick reading, or
an in-depth study?
    Quick reading and I have followed the discussion closely.

On Sat, Oct 1, 2016 at 4:39 AM, Howard Lovatt via swift-evolution <
swift-evolution at swift.org> wrote:

> Comments on: 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/proposa
> ls/0143-conditional-conformances.md
>
>
>    - What is your evaluation of the proposal?
>
> Great
>
>    - Is the problem being addressed significant enough to warrant
>    a change to Swift?
>
> Yes
>
>    - Does this proposal fit well with the feel and direction of Swift?
>
> Yes
>
>    - If you have used other languages or libraries with a
>    similar feature, how do you feel that this proposal compares to those?
>
> No
>
>    - How much effort did you put into your review? A glance, a
>    quick reading, or an in-depth study?
>
> Having written my own collection library and also extended the existing
> one I have hit this limitation and would therefore welcome this addition.
>
> On Thursday, 29 September 2016, Joe Groff <jgroff at apple.com> 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/proposa
>> ls/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
>>
>> 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/proposa
>> ls/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
>>
>> Thank you,
>>
>> -Joe
>>
>> Review Manager
>>
>
>
> --
> -- Howard.
>
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20161002/8de7fc9c/attachment.html>