What is your evaluation of the proposal?
+1
Is the problem being addressed significant enough to warrant a change to
Swift?
Yes. A thousand times 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 compares well. Same type requirements for generic parameters are
sorely missed though.
How much effort did you put into your review? A glance, a quick reading, or
an in-depth study?
I've followed the discussion closely and given input a couple times.
More information about the Swift evolution process is available at
On Sun, Sep 25, 2016 at 6:39 AM, Dave Abrahams via swift-evolution <
swift-evolution@swift.org> wrote:
>
> on Fri Sep 23 2016, Douglas Gregor <swift-evolution@swift.org> wrote:
>
> > What is your evaluation of the proposal?
>
> It's ought to be obvious, but +1; when can I have it?
>
> > Is the problem being addressed significant enough to warrant a change
> > to Swift?
>
> Indeed.
>
> > 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?
>
> I haven't, except maybe Haskell.
>
> > How much effort did you put into your review? A glance, a quick
> > reading, or an in-depth study?
>
> All that and more.
>
> Cheers,
> --
> -Dave
>
> _______________________________________________
> swift-evolution mailing list
> swift-evolution@swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
>
_______________________________________________
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution
