Swift vs Obj-C exceptions. What is stack unwinding? Why doesn't Swift do it?

Question

There is a note in the Swift Docs that states the following:

Error handling in Swift resembles exception handling in other languages, with the use of

Answer 1

Unwinding the stack basically means that when an exception is thrown, the method is immediately interrupted, the caller of the method is immediately interrupted and so on until an exception handler (try-catch-finally) is found or until we reach the top of the stack, when the exception usually ends in interrupting the current thread.

That works pretty well in languages with a garbage collector but in general it can lead to memory leaks in languages with manual memory management. Also, since methods are interrupted in unexpected places, an exception often leads to undefined/unrecoverable program states.

That's why exception in all languages should be used sparingly and only to handle exceptional situations, not to handle normal program flow.

Obj-C exceptions weren't very good, with all the problems mentioned above (see NSException, @try-@catch-@finally), that's why nobody is using them. Instead, Obj-C came with error parameters (you pass a reference to a NSError variable and if the method fails, the error gets assigned into that variable). See Error Handling in Objective-C

Swift just came with another syntax for NSError. It's not a real exception handling (errors don't interrupt program execution). See Error Handling in Swift

Technically, every function/method that can throw an error in Swift only has an additional hidden parameter that is used to pass the error back to caller context.

If you want more information, just compare code in Swift 1.x and 2.x (1.x didn't have special grammar for error handling yet).