<div dir="ltr"><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"><<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"><span class=""><br>
> (in Smalltalk, like in Swift?, if i remember correctly, ‘self’ is implicitly<br>
> returned in absence of a return value and can be ignored.<br>
</span>I'm a big fan of returning self — its much more useful than void…<br>
But it seems the Swift-community doesn't like method chaining.<br>
<div class="HOEnZb"><div class="h5"><br></div></div></blockquote><div><br></div><div>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><br></div><div>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>