[swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions
jeremy.j.pereira at googlemail.com
Mon Dec 14 09:29:38 CST 2015
> On 14 Dec 2015, at 09:01, Andrew Brown via swift-evolution <swift-evolution at swift.org> wrote:
> This discussion isn't going to be solved quickly so +1 for a compiler flag.
> I'd propose the flag generates an error if member variables are accessed without self.
I’d propose it only be a warning. The reason for this is that Chris Lattner, in an unrelated thread, expressed an aversion to compiler flags that create different dialects of the language and I agree with him.
> Then after some time we can survey the community (or scan GitHub) to see how many people use the flag.
> (making it a preference in Xcode would also help)
>> On 14 Dec 2015, at 07:12, David Hart via swift-evolution <swift-evolution at swift.org> wrote:
>>> On 13 Dec 2015, at 22:45, Charles Srstka via swift-evolution <swift-evolution at swift.org> wrote:
>>> Since opinions seem to be divided on this, how about adding an optional warning flag to the compiler, which would warn if one accessed an instance variable or method without self. in front?
>> That is a good alternative.
>> swift-evolution mailing list
>> swift-evolution at swift.org
> swift-evolution mailing list
> swift-evolution at swift.org
More information about the swift-evolution