> IMHO, it's a more elegant solution to the same problem. I might be worth 
> pursuing it despite the breaking change because it has more chance of being 
> considered than pure syntactic sugar which the core team is not even 
> considering before Swift 4.

Besides, if I understood correctly I think now is the good time to submit 
breaking proposals.

_______________________________________________
swift-evolution mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-evolution

Reply via email to