<p dir="ltr">Looks like the conversation is going in circles a bit. I believe Chris Lattner said he was opposed to any compiler flags that would lead to different dialects of Swift, and it's a valid concern, so I'm not sure how feasible an optional compiler flag would be. </p>
<br><div class="gmail_quote"><div dir="ltr">On Mon, Dec 14, 2015, 8:48 PMÂ Kenny Leung via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">This sounds like a candidate for a compiler option to add a warning (or error) if you leave out self. It adds no overhead to the language, but if you like it, you can enforce it.<br>
<br>
-Kenny<br>
<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>