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

[Rudolf Adamkovic]

+1

1) I actually encountered at least two bugs in my app introduced by this implicit "self" behavior. It can be dangerous and hard to track down.

2) Also when, say fine-tuning UIKit animations, I find myself wasting enormous amount of time adding and removing "self".

R+

Sent from my iPhone

> On 04 Dec 2015, at 22:19, 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
> https://lists.swift.org/mailman/listinfo/swift-evolution