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 > <swift-evolution@swift.org> wrote: > > 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 > you feel that this proposal compares to those? > N/A > > How much effort did you put into your review? A glance, a quick reading, or > an in-depth study? > In-depth study, I ran into a situation where I needed something like this > some time ago. > > >> On Mar 24, 2016, at 1:54 PM, Douglas Gregor <dgre...@apple.com >> <mailto:dgre...@apple.com>> 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 >> >> <https://github.com/apple/swift-evolution/blob/master/proposals/0048-generic-typealias.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/0048-generic-typealias.md >> >> <https://github.com/apple/swift-evolution/blob/master/proposals/0048-generic-typealias.md> >> Reply text >> >> Other replies >> <https://github.com/apple/swift-evolution#what-goes-into-a-review-1>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, >> >> Doug Gregor >> >> Review Manager >> >> _______________________________________________ >> swift-evolution-announce mailing list >> swift-evolution-annou...@swift.org >> <mailto:swift-evolution-annou...@swift.org> >> https://lists.swift.org/mailman/listinfo/swift-evolution-announce > > _______________________________________________ > 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
