On Jan 4, 2018, at 3:43 PM, Nevin Brackett-Rozinsky
<nevin.brackettrozin...@gmail.com> wrote:
>
> There’s a lot of information here and it’ll take some time to process it all.
> My initial reaction is that a “strong type-alias” feature might help. If one
> could write (strawman syntax):
>
> strong typealias Dog = PyVal // A semantically independent new type
>
> extension Dog {
> // Declarations here are only available on “Dog”, not on “PyVal”
> }
>
> then most of the overload issues would evaporate.
Until and if there were an acceptable design for such a feature, it is
impossible to say whether it would help. I am personally skeptical that
"strong type aliases" will ever make it into Swift.
-Chris
_______________________________________________
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution
