What is your evaluation of the proposal? +1. Especially for forcing the alias side of the declaration to explicitly keep track of type constraints.
Is the problem being addressed significant enough to warrant a change to Swift? Yes. Previously, one could "work around" this by declaring a 0-case generic enum with associated type "projections". I'm glad to see that pattern find a formal place in the language. 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? This proposal brings Swift up to par with languages that allow any kind of "alias"ing of types, whether that be C++ or Haskell [in a cleaner way than the former]. How much effort did you put into your review? A glance, a quick reading, or an in-depth study? In-depth study. I actually took a crack at an implementation a while ago! ~Robert Widmann 2016/03/24 12:54、Douglas Gregor via swift-evolution <swift-evolution@swift.org> のメッセージ: > 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 > 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 > 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 > Reply text > > Other replies > 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 > Thank you, > > Doug Gregor > > Review Manager > > _______________________________________________ > 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
