[swift-evolution] [swit-evolution] [Review] SE-0156: Class and Subtype existentials

Kevin Nattinger swift at nattinger.net
Wed Mar 1 03:10:58 CST 2017

> What is your evaluation of the proposal?
The core of the proposal is unquestionably necessary to correct a serious deficiency in the expressivity of the type system, but I take issue with the arbitrary limitation of requiring the concrete type to be first and would give a full +1 to the core team accepting with the modification of removing that limitation.

> Is the problem being addressed significant enough to warrant a change to Swift?
Definitely. I’ve run into the issue this would solve several times in real-world applications.

> 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?
Basically a direct translation of the objc feature.

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

Followed and to some extent participated in the discussion, relatively quick read of the final proposal.

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

More information about the swift-evolution mailing list