+111eleventyone
Also, FWIW, strong +1 for everything in the generics manifesto, too.
Sent from my iPhone
> On Sep 23, 2016, at 18:50, Douglas Gregor via swift-evolution
> wrote:
>
> Hello Swift community,
>
> The review of SE-0142: "Permit where clauses to
Sent from my iPhone
> On Sep 24, 2016, at 6:55 PM, Nate Cook wrote:
>
>
>> https://github.com/apple/swift-evolution/blob/master/proposals/0142-associated-types-constraints.md
>
>> What is your evaluation of the proposal?
> [Smiling Face With Heart-Shaped Eyes Emoji]
>
>
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
on Fri Sep 23 2016, Douglas Gregor 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
> https://github.com/apple/swift-evolution/blob/master/proposals/0142-associated-types-constraints.md
> What is your evaluation of the proposal?
[Smiling Face With Heart-Shaped Eyes Emoji]
One of the examples given (associatedtype SubSequence : Sequence where
SubSequence...) looks like it
+1. Very much looking forward to the richness this will add to the generic
system.
-Matt
> On Sep 23, 2016, at 16:50, Douglas Gregor via swift-evolution
> wrote:
>
> Hello Swift community,
>
> The review of SE-0142: "Permit where clauses to constrain associated
>
> What is your evaluation of the proposal?
+1. This is a great enhancement that I have wanted ever since Swift was
released.
> Is the problem being addressed significant enough to warrant a change to
> Swift?
Yes. It allows us to express our intentions much more clearly and concisely.
>
> What is your evaluation of the proposal?
+1, like others I would love to have this feature available today, as my code
is currently littered with complicated constraints on types that could be much
more elegantly handled by constraints on the associated types themselves.
> Is the problem
Strong +1. I really need this feature to improve and simplify my existing code.
> On Sep 23, 2016, at 5:50 PM, Austin Zheng via swift-evolution
> wrote:
>
> * What is your evaluation of the proposal?
>
> +1. I very much want to see this in Swift, and it seems like
* What is your evaluation of the proposal?
+1. I very much want to see this in Swift, and it seems like a logical
progression that has the potential to eliminate ugly workarounds.
* Is the problem being addressed significant enough to warrant a change to
Swift?
Yes. Right now the desired
Hello Swift community,
The review of SE-0142: "Permit where clauses to constrain associated types"
begins now and runs through September 30, 2016. The proposal is available here:
https://github.com/apple/swift-evolution/blob/master/proposals/0142-associated-types-constraints.md
Reviews are an
11 matches
Mail list logo