<div dir="ltr"><div>It has already been brought up in the (multiple) mail chains named "<a href="https://lists.swift.org/pipermail/swift-evolution/2015-December/000209.html" target="_blank">Proposal: Re-instate mandatory self for accessing instance properties and functions</a><a name="1517dc5068f5c603_209"></a>".<br></div>You can find more threads and replies to that discussion at <a href="https://lists.swift.org/pipermail/swift-evolution/" target="_blank">https://lists.swift.org/pipermail/swift-evolution/</a>.<br><div class="gmail_extra"><br></div><div class="gmail_extra">—Johan<br><br></div><div class="gmail_extra"><div class="gmail_quote">On Mon, Dec 7, 2015 at 6:21 PM, Florian Reinhart via swift-evolution <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br>
<br>
I prefer prefixing property (and method) access with self. in my code. This makes it immediately obvious if a variable is local to the function or actually a property of the instance.<br>
<br>
I assume this has already been discussed and would like to know why it was decided to not require self for property and method access.<br>
<br>
—Florian<br>
_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
</blockquote></div><br></div></div>