[swift-evolution] [Proposal] Type Narrowing

David Hart david at hartbit.com
Wed Nov 9 00:51:10 CST 2016

> On 3 Nov 2016, at 20:23, Nevin Brackett-Rozinsky via swift-evolution <swift-evolution at swift.org> wrote:
> This looks like a lot of complexity for very little gain.
> Aside from any implementation concerns, this proposal substantially increases the cognitive load on developers. To figure out what a piece of code means, someone reading it will have to mentally keep track of a “type stack” for every variable. That is the opposite of “clarity at the point of use”.

Very well said. I think this is perhaps the number one complaint I have about the proposal.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20161109/b57ab847/attachment.html>

More information about the swift-evolution mailing list