Combining ? with throwing when there's no reasonable default

[Ray_Fix]

I feel bridging the worlds of nil failing and throwing initializers with as little friction as possible is important. There is a tendency I have noticed in myself to nil coalesce to a bogus value that I'll fix real soon(TM). But if I have the right tool to reach for, I am more likely to do the right thing.

I proposed a slightly different (non-operator) spelling:

Throw on nil

I find myself wanting to define an operation that converts failable initializers to throwing ones. When I have a throwing initializer contains multiple failing initializers, I think it improves the clarity and readability of the code. (see below) UPDATE: Leaving the original implementation but I am not opposed to changing the spelling or making this an operator or whatever. Lots of great ideas and info below. extension Optional { func orThrow(_ error: @autoclosure () -> Error) throws -> W…