[swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions

Colin Cornaby colin.cornaby at mac.com
Fri Dec 4 17:29:41 CST 2015


I've had a lot of weird things happen that I've traced to mistakes in properties having the same name as function arguments. I've hardly ever had this issue in modern Obj-C.

I'm a little more ok with functions not needing self as it's less likely for those to shadow something like an argument, but I guess the consistency would be nice too.

On Dec 04, 2015, at 01:20 PM, David Hart <david at hartbit.com> wrote:

I don't understand the reasoning behind removing the need to access instance properties and functions using self. Swift has always seemed to prefer readability to brevity and the feature makes the distinction between local and instance variables/functions crystal clear. Any good reason I shouldn't go on with the proposition?

Just as example, my proposition makes the following piece of code illegal:

struct FooBar {
var foo: String = "foobar"

func bar() {
print(foo) // compiler error
print(self.foo) // compiler happy

func bar2() {
bar() // compiler error
self.bar() // compiler happy
swift-evolution mailing list
swift-evolution at swift.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20151204/d4b8d3e8/attachment.html>

More information about the swift-evolution mailing list