> After all… you clearly don’t know about your current state, so how can you > know how to correctly recover from it?
This a bit of a stretch, it is often the case but not a necessary conclusion. Both C++ and Java have a model where it is not uncommon to recover from exceptions instead of crashing. You might know enough about your context to be able to go back to a safe point in time/app lifecycle and resume from there. Also, the more scenarios we want to code in pure Swift in the more cases in which other languages offer features we do not want in Swift now we are going to encounter. The pragmatic voice in engineers will start asking "why do I need to jump through hoops for purity's sake"? Sent from my iPhone > On 12 Jul 2016, at 09:10, Rod Brown via swift-evolution > <swift-evolution@swift.org> wrote: > > After all… you clearly don’t know about your current state, so how can you > know how to correctly recover from it? _______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
