Is there any difference in how exceptions are handled under the hood between 'try?' and 'do/catch'?

[phoneyDev (Stern)]

Swift code can't catch Obj-C exceptions and a swift app will crash if an Obj-C exception finds its way into swift code. See for instance:

Catching NSException

Apologies if this has come up before - I've fallen behind in following this list. I recently ran into an issue where I needed to be able to catch NSExceptions raised by Objective C API in Swift, and found no good way to do that. Currently the only possible way is to via Objective C code that wraps the call in an Objective C style @try/@catch block. If building a swift framework, this means a separate module, since we can't use bridging headers. My quick attempt at a workaround can be s…

A tricky situation that the language seems to have no support for. (Exceptions, Extensions, Properties)

Try this in an iOS/macOS SpriteKit project: let spriteSize = CGSize(width: 32, height: 32) let sprite1 = SKSpriteNode(color: .red, size: spriteSize) let sprite2 = SKSpriteNode(color: .green, size: spriteSize) let physicsBody1 = SKPhysicsBody(rectangleOf: spriteSize) sprite1.physicsBody = physicsBody1 scene.addChild(sprite1) sprite2.physicsBody = physicsBody1 scene.addChild(sprite2) It will crash during runtime: Terminating app due to uncaugh…

Why are FileHandle methods deprecated without warnings, and how do I show the warnings?

Just a point of clarification here: they can trigger exceptions, but aren't marked with throw You’re comparing apples to oranges here. The exceptions thrown by these legacy APIs are Objective-C language exceptions [1]. There are very different from Swift errors and Swift can’t deal with them at all. The Objective-C equivalent of a Swift error is an NSError output parameter. Share and Enjoy Quinn “The Eskimo!” @ DTS @ Apple [1] On most platforms such exceptions are equivalent to C++ exc…

Nothing has changed.