<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></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 May 25, 2016, at 1:00 PM, Adriano Ferreira <<a href="mailto:adriano.ferreira@me.com" class="">adriano.ferreira@me.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Hi all,</div><div class=""><br class=""></div>I really like this idea and appreciate the effort. However, I’d rather have a method similar to <a href="http://apidock.com/rails/Object/tap" class="">Ruby Object#tap</a> and not a free function.<div class=""><br class=""></div><div class=""><div class="">Well, since there’s no "Object class" in Swift, the way I see it is through a protocol, much like the <a href="https://github.com/devxoul/Then" class="">Then</a> project is done.<br class=""><div class=""><br class=""></div><div class="">— A</div></div></div></div></div></blockquote><div><br class=""></div><div>In Swift, there's no root object like NSObject, which is what the Then project relies upon. I'm unfamiliar with `tap` but it looks</div><div>similar to method cascading, which is on hold for Swift 4.</div><div><br class=""></div><div>-- E</div><div><br class=""></div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><div class=""><div class=""><div class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On May 25, 2016, at 2:28 PM, Erica Sadun 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=""><meta http-equiv="Content-Type" content="text/html charset=us-ascii" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Over the past couple of days, the Twitters have discovered some work I'd done on closure-based setup. <div class="">It's clear that a demand is out there and strong for this kind of behavior, even without implicit `self` as </div><div class="">part of the mix or cascading. In that light, I've put together the following:<div class=""><br class=""></div><div class=""><a href="https://gist.github.com/erica/96d9c5bb4eaa3ed3b2ff82dc35aa8dae" class="">https://gist.github.com/erica/96d9c5bb4eaa3ed3b2ff82dc35aa8dae</a></div><div class=""><br class=""></div><div class="">If the community demand is this high, I think we should re-consider pushing it before 3. </div><div class="">Feedback as always welcome, including criticism.</div></div></div></div></blockquote></div></div></div></div></div></div></div></blockquote></div><br class=""></body></html>