<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div></div><div>-1</div><div>I can't see a significant advantage over using the library based approach where the receiver is clearly recognizable and no context problems arise.</div><div><br></div><div>-Thorsten </div><div><br>Am 14.04.2016 um 19:03 schrieb Erica Sadun via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>>:<br><br></div><blockquote type="cite"><div><meta http-equiv="Content-Type" content="text/html charset=utf-8"><br class=""><div><blockquote type="cite" class=""><div class="">On Apr 14, 2016, at 10:42 AM, Jonathan Tang via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote">On Thu, Apr 14, 2016 at 8:23 AM, Tino Heth via swift-evolution <span dir="ltr" class=""><<a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br class="">
> (in Smalltalk, like in Swift?, if i remember correctly, ‘self’ is implicitly<br class="">
> returned in absence of a return value and can be ignored.<br class="">
</span>I'm a big fan of returning self — its much more useful than void…<br class="">
But it seems the Swift-community doesn't like method chaining.<br class="">
<div class="HOEnZb"><div class="h5"><br class=""></div></div></blockquote><div class=""><br class=""></div><div class="">I dunno about that... AlamoFire and SwiftyJSON both use it, and are quite popular with rank-and-file Swift programmers. It's certainly not popular in the Objective-C community (where the syntax doesn't really support it), but it seems like the Swift community may be warming up to it.</div><div class=""><br class=""></div><div class="">I also like the idea of a dedicated method-cascading operator, like what Dart has. It eliminates the need for a programmer to explicitly remember to 'return self' at the end of a chainable method. Not sure how well it'd integrate with SE-0047 (@discardableResult) though.</div></div></div></div></div></blockquote><br class=""></div><div>Method cascades draft: <a href="https://gist.github.com/erica/6794d48d917e2084d6ed" class="">https://gist.github.com/erica/6794d48d917e2084d6ed</a></div><div><br class=""></div><div>deferred to after 3.0</div><div><br class=""></div><div>-- E</div><div><br class=""></div><div><br class=""></div><br class=""></div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>swift-evolution mailing list</span><br><span><a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a></span><br><span><a href="https://lists.swift.org/mailman/listinfo/swift-evolution">https://lists.swift.org/mailman/listinfo/swift-evolution</a></span><br></div></blockquote></body></html>