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
([email protected]) 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.
_______________________________________________
swift-evolution mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-evolution
