> On 3 Nov 2016, at 20:23, Nevin Brackett-Rozinsky via swift-evolution
> <[email protected]> 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.
_______________________________________________
swift-evolution mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-evolution
