[swift-evolution] [Review] Replace `typealias` keyword with `associatedtype` for associated type declarations

James Campbell james at supmenow.com
Tue Jan 12 04:23:21 CST 2016


+1 In the original discussion I was advocating generics as the way forward

On Tue, Jan 12, 2016 at 10:19 AM, Howard Lovatt via swift-evolution <
swift-evolution at swift.org> wrote:

> I have proposed the elimination of associated types by replacing them with
> generic arguments and an implementation of generics that allows covariance,
> see:
>
> [swift-evolution] Make generics covariant and add generics to protocols
> <https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20160111/006367.html>
>
>
> Food for though for another way forward?
>
> PS I agree using typealias for two different concepts is confusing.
>
>
> On 3 Jan 2016, at 5:38 PM, Douglas Gregor via swift-evolution <
> swift-evolution at swift.org> wrote:
>
> Hello Swift community,
>
> The review of "Replace `typealias` keyword with `associatedtype` for
> associated type declarations” begins now and runs through Wednesday,
> January 6th. The proposal is available here:
>
>
> https://github.com/apple/swift-evolution/blob/master/proposals/0011-replace-typealias-associated.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.
>
> 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 you 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
>
> Cheers,
> Doug Gregor
> Review Manager
>
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
>
>
>
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
>
>


-- 
 Wizard
james at supmenow.com
+44 7523 279 698
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160112/6ce285d0/attachment.html>


More information about the swift-evolution mailing list