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 you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those? NA How much effort did you put into your review? A glance, a quick reading, or an in-depth study? Pretty brief, read through the proposal early on and was reaching for this functionality a few days ago. > On Mar 24, 2016, at 9:54 AM, Douglas Gregor <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 > 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
