[swift-evolution] [swift-evolution-announce] [Review] Require self for accessing instance members

Pierre Monod-Broca pierre at monod-broca.fr
Thu Dec 17 02:03:32 CST 2015

* What is your evaluation of the proposal?

I’m strongly against it.

* Is the problem being addressed significant enough to warrant a change to Swift?

I don’t think so.

I, personally, never encountered a bug due to this problem, and it would be really easy to fix.

I hear that such bugs might be difficult to track, and there might be ways to help to detect them, but I’m not convinced by the proposed solution.

It seems more like a matter of taste, and the proposed solution would remove choice.

* Does this proposal fit well with the feel and direction of Swift?

I don’t think so.

I think Swift should be concise when that doesn’t hinder clarity. (And in this case, I’m afraid it is explicitness that would hinder clarity).

Also, it seems to me implicit self makes properties and methods first-class citizens, and I think they should be.

* If you have you used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?

Yes: Objective-C, and I was glad, migrating to Swift, to get rid of all those explicit self.

* How much effort did you put into your review? A glance, a quick reading, or an in-depth study?

I followed most of the thread.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20151217/8584e884/attachment.html>

More information about the swift-evolution mailing list