<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 Oct 9, 2017, at 9:02 AM, Dave DeLong 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=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Oooo, I really like this.<div class=""><br class=""></div><div class="">It also brings up an interesting point on the whole async discussion. Doesn’t the async apply to the <i class="">return value</i> and not the other stuff?</div></div></div></blockquote><div><br class=""></div>No, the whole function <i class="">including any side effects</i> gets executed asynchronously. "Pure" functions could (sorta) be regarded as only having the "async" apply to the return value, but that mental model is incorrect and it only gives the right "answer" as a consequence of the function being pure.</div><div><br class=""></div><div>At least, if I understand things correctly.</div><div><br class=""></div><div>- Dave Sweeris</div></body></html>