Re: [swift-evolution] [swift-evolution-announce] [Review] SE-0048: Generic Type Aliases

On Thu, Mar 24, 2016, at 09:54 AM, Douglas Gregor wrote: > What is your evaluation of the proposal? Strong +1 here. I've wanted this since day one. In fact, I filed ticket SR-64 to cover adding this a while ago. > * Is the problem being addressed significant enough to warrant a >change to

Re: [swift-evolution] [swift-evolution-announce] [Review] SE-0048: Generic Type Aliases

> https://github.com/apple/swift-evolution/blob/master/proposals/0048-generic-typealias.md >• What is your evaluation of the proposal? +1 I think it is a very important feature to enable working with more complicated generic types while maintaining readability. I do not agree with the

Re: [swift-evolution] [swift-evolution-announce] [Review] SE-0048: Generic Type Aliases

> On Mar 29, 2016, at 10:14 AM, Dave Abrahams via swift-evolution > wrote: > > > I'm not objecting at all. It's an obvious thing for us to do, and we > should do it at some point. It just doesn't seem very impactful or > crucial. I use typealiases as a form of

Re: [swift-evolution] [swift-evolution-announce] [Review] SE-0048: Generic Type Aliases

This feature removes the need, in specific cases, for wrapping a function in a struct 'just for' the ability to use generics. ```swift typealias Parser = String -> Output // can now, sometimes, replace struct Parser { let transform: String -> Output init(transform: String -> Output) {

Re: [swift-evolution] [swift-evolution-announce] [Review] SE-0048: Generic Type Aliases

On Mar 24, 2016, at 1:18 PM, Dave Abrahams via swift-evolution wrote: >> >> Is the problem being addressed significant enough to warrant a change >> to Swift? > > That's my biggest question about this proposal. Yes, as the proposal > says, generic type aliases fill

Re: [swift-evolution] [swift-evolution-announce] [Review] SE-0048: Generic Type Aliases

on Thu Mar 24 2016, Dave Abrahams wrote: > on Thu Mar 24 2016, Douglas Gregor wrote: > >> Hello Swift community, >> >> The review of SE-0048 "Generic Type Aliases" begins now and runs >> through March 29, 2016. The proposal is available here: >> >>

Re: [swift-evolution] [swift-evolution-announce] [Review] SE-0048: Generic Type Aliases

on Thu Mar 24 2016, Douglas Gregor wrote: > Hello Swift community, > > The review of SE-0048 "Generic Type Aliases" begins now and runs through > March 29, 2016. The proposal is available here: > > https://github.com/apple/swift-evolution/blob/master/proposals/0048-generic-typealias.md >

Re: [swift-evolution] [swift-evolution-announce] [Review] SE-0048: Generic Type Aliases

> What is your evaluation of the proposal? +1 > 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

Re: [swift-evolution] [swift-evolution-announce] [Review] SE-0048: Generic Type Aliases

> https://github.com/apple/swift-evolution/blob/master/proposals/0048-generic-typealias.md > • What is your evaluation of the proposal? I think it's a good idea that will make a lot of code clearer. I agree with the decision not to support additional constraints on the generic type.

Re: [swift-evolution] [swift-evolution-announce] [Review] SE-0048: Generic Type Aliases

> What is your evaluation of the proposal? Big +1. I would prefer to see it go further to allow arbitrary constraints, but it is a big step forward and that can come in the future. > Is the problem being addressed significant enough to warrant a change to > Swift? Yes > Does this proposal fit

Re: [swift-evolution] [swift-evolution-announce] [Review] SE-0048: Generic Type Aliases

Strong +1 from me, too. With the exact response as Juan. It is among the top 10 on my wish list. > On Mar 24, 2016, at 11:18 AM, Juan Ignacio Laube via swift-evolution > wrote: > > What is your evaluation of the proposal? > A strong +1 on this. > > Is the problem

Re: [swift-evolution] [swift-evolution-announce] [Review] SE-0048: Generic Type Aliases

What is your evaluation of the proposal? A strong +1 on this. 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

Re: [swift-evolution] [swift-evolution-announce] [Review] SE-0048: Generic Type Aliases

What is your evaluation of the proposal? +1, originally I hadn’t seen the value, but ran into wanting this just the other day. 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? Very much so. If