[swift-evolution] DynamicMemberLookup proposal: status update

Chris Lattner clattner at nondot.org
Thu Jan 4 19:01:29 CST 2018

On Jan 4, 2018, at 3:43 PM, Nevin Brackett-Rozinsky <nevin.brackettrozinsky at 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.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20180104/c47fcc32/attachment.html>

More information about the swift-evolution mailing list