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

Janosch Hildebrand jnosh at jnosh.com
Sun Jan 3 07:42:51 CST 2016

> On 03 Jan 2016, at 07:38, Douglas Gregor <dgregor at apple.com> wrote:
> 	* What is your evaluation of the proposal?

I am in favor of this for the same reasons mentioned by the previous reviewers.

> 	* 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?

I think so. 

> 	* If you have you used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?

I am only aware of Rust and I haven't used that enough to make any meaningful comparisons.

> 	* How much effort did you put into your review? A glance, a quick reading, or an in-depth study?

I read the proposal and followed the previous threads discussing the proposal and the keyword.

Speaking of which, `associatedtype` remains my favorite. I don't think its ideal but I prefer it to the alternatives that were considered.

> 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>
> 	Cheers,
> 	Doug Gregor
> 	Review Manager
> _______________________________________________
> swift-evolution-announce mailing list
> swift-evolution-announce at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution-announce

- Janosch

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160103/e31d438a/attachment.html>

More information about the swift-evolution mailing list