[swift-evolution] Revisiting SE-0110

Adrian Zubarev adrian.zubarev at devandartist.com
Sat Jun 17 11:23:48 CDT 2017

I can only agree here, the language suffers from shortcuts like that. Same goes for access modifier on extensions, or `indirect` before enums and as already mentioned before me labeled tuple destructuring.

Adrian Zubarev
Sent with Airmail

Am 17. Juni 2017 um 18:09:50, Matthew Johnson via swift-evolution (swift-evolution at swift.org) schrieb:

#2 is debatable. It would solve an enum-based parallel to Chris’s original:

case let .foo(a: Int, b: String)  // disallowed
case .foo(a: let Int, b: let String)  // allowed, and Int/String no longer look like types

Doing this with #2 is what I suggested earlier.  I like this because I find the disallowed style to have too much cognitive load anyway.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20170617/fcbc7979/attachment.html>

More information about the swift-evolution mailing list