> On 09 Nov 2016, at 07:51, David Hart via swift-evolution > <swift-evolution@swift.org> wrote: > > >> On 3 Nov 2016, at 20:23, Nevin Brackett-Rozinsky via swift-evolution >> <swift-evolution@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.
Exactly. -1. Regards, Rien Site: http://balancingrock.nl Blog: http://swiftrien.blogspot.com Github: http://github.com/Swiftrien Project: http://swiftfire.nl _______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
