Re: [swift-users] Asynchronous error recovering with RecoverableError

2017-03-28 Thread Michael Ilseman via swift-users
New start task: https://bugs.swift.org/browse/SR-4405 Add @escaping to RecoverableError.attemptRecovery > On Mar 28, 2017, at 3:31 PM, Douglas Gregor wrote: > > >> On Mar 28, 2017, at 11:21 AM, Michael Ilseman

Re: [swift-users] Asynchronous error recovering with RecoverableError

2017-03-28 Thread Douglas Gregor via swift-users
> On Mar 28, 2017, at 11:21 AM, Michael Ilseman wrote: > > CC Doug Gregor, who git blame tells me wrote this part. > > Doug, this slightly predates noescape-by-default. Is this a bug or as > intended? It’s a bug; the point here is that we can do recovery asynchronously,

Re: [swift-users] Asynchronous error recovering with RecoverableError

2017-03-28 Thread Michael Ilseman via swift-users
CC Doug Gregor, who git blame tells me wrote this part. Doug, this slightly predates noescape-by-default. Is this a bug or as intended? > On Mar 28, 2017, at 8:49 AM, Elia Cereda via swift-users > wrote: > > Hi Dennis, > > Thanks for your answer. I can see that my

Re: [swift-users] Asynchronous error recovering with RecoverableError

2017-03-28 Thread Elia Cereda via swift-users
Hi Dennis, Thanks for your answer. I can see that my message needs some more context: RecoverableError is a protocol in the standard library that can be implemented to opt in to the error recovery mechanism available on macOS. attemptRecovery(optionIndex, resultHandler:) is one of the methods

Re: [swift-users] Asynchronous error recovering with RecoverableError

2017-03-23 Thread Elia Cereda via swift-users
I'd like to bump this issue, since it has been some time and it hasn't been addressed. Thanks, Elia Cereda > Il giorno 03 mar 2017, alle ore 21:33, Elia Cereda ha > scritto: > > I’m wondering why the resultHandler block on >