[swift-evolution] Making `.self` After `Type` Optional

Tanner Nelson me at tanner.xyz
Tue Mar 15 14:32:27 CDT 2016

> On Mar 15, 2016, at 1:54 AM, Charles Constant <charles at charlesism.com> wrote:
> +1 for junking the .self requirement
> On Wed, Mar 9, 2016 at 11:14 PM, David Hart via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
> I strongly agree for the removal of .self. I remember it being a great source of confusion when I first learned Swift.
> I had the same experience. It was very disorienting. 
> Now that Dave and Joe have explained its origin as a safety feature, it makes sense. The problem is that there's no way to convey that to the end-user, so it seems like it has some deeper meaning. Then you start second-guessing yourself if there's an error in your code, etc.

I agree. Swift's type-checking engine is strong enough to merit not needing the redundant `.self` safety check. It feels like I'm doing something wrong when I need to use `.self`. 

> Nice to see that this might be fixed. Evolution is making me happier and happier lately :)

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

More information about the swift-evolution mailing list