<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=""><div class="">I’m wondering why the resultHandler block on RecoverableError.attemptRecovery(optionIndex, resultHandler:) is not marked @escaping?</div><div class=""><br class=""></div><div class="">I’m trying to invoke some recovering code that executes asynchronously, then reports if it was successful or not and I thought that this was the right strategy. As far as I can tell, without @escaping that method loses all it’s purpose and becomes essentially equivalent to attemptRecovery(optionIndex:).</div><div class=""><br class=""></div><div class="">So, I’d like to ask.</div><div class="">1. Is it a bug or that method is non-escaping on purpose?</div><div class="">2. If it is a bug, is there a workaround that can be applied pending a fix in a future version of Swift?</div><div class="">3. If it was a deliberate decision, what's the supported method of asynchronously invoking error recovery code?</div><div class=""><br class=""></div><div class="">Seeing that this wasn’t changed in Xcode 8.3b2, I think it unlikely that this was an oversight.</div><div class=""><br class=""></div>Thanks,<br class=""><div class="">
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;">Elia Cereda</div>
</div>
<br class=""></body></html>