<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Apr 7, 2016, at 6:17 AM, Brent Royal-Gordon via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><div class=""><div class="">Having said all this, now that we have `#Self`, I'm wondering if we still want `Self` in value types. The two are *exactly* equivalent in value types as far as I can tell, and `Self` in classes implies dynamic behavior which is not supported by value types. The use of `Self` in class member bodies is a clean win, the existence of `#Self` is a clean win, but I'm not sure we need the value type thing too.<br class=""></div></div></blockquote></div><br class=""><div class="">I prefer the consistency that it be available across types without exception more than I care that the functionality is duplicated. Plus if Swift eventually introduces derived value types, it may play a bigger role.</div><div class=""><br class=""></div><div class=""><a href="http://thread.gmane.org/gmane.comp.lang.swift.evolution/12644/" class="">http://thread.gmane.org/gmane.comp.lang.swift.evolution/12644/</a></div><div class=""><a href="http://thread.gmane.org/gmane.comp.lang.swift.evolution/10652" class="">http://thread.gmane.org/gmane.comp.lang.swift.evolution/10652</a></div><div class=""><a href="http://thread.gmane.org/gmane.comp.lang.swift.evolution/153" class="">http://thread.gmane.org/gmane.comp.lang.swift.evolution/153</a></div><div class=""><br class=""></div><div class="">-- E</div><div class=""><br class=""></div></body></html>