Hi all,
Now that phase 2 has begun, am I able to submit a proposal for this?
Best regards,
Jack
> On 8 Feb 2017, at 20:00, Jack Newcombe wrote:
>
> Hi all,
>
> Currently there are a number of different operators for dealing with
> optionals that cover most of the use cases. However, I think
ake sense to add to the standard library.
>
> On Feb 9, 2017, at 12:04 AM, Jack Newcombe via swift-evolution <
> swift-evolution@swift.org> wrote:
>
> This can actually be accomplished now using a closure:
>
> let value = optionalValue ?? { throw CustomError.failure }(
-coalescing operator is that it means allowing
the second operand to be a statement rather than an expression, which I assume
would be seen as an unacceptable.
> On 9 Feb 2017, at 07:56, Brent Royal-Gordon wrote:
>
>> On Feb 8, 2017, at 12:00 PM, Jack Newcombe via swift-evolutio
sing the ‘!’
> operator for something else that fatal error.
>
>> Le 8 févr. 2017 à 21:00, Jack Newcombe via swift-evolution
>> mailto:swift-evolution@swift.org>> a écrit :
>>
>> Hi all,
>>
>> Currently there are a number of different operators f
operator for something else that fatal error.
>
>> Le 8 févr. 2017 à 21:00, Jack Newcombe via swift-evolution
>> mailto:swift-evolution@swift.org>> a écrit :
>>
>> Hi all,
>>
>> Currently there are a number of different operators for dealing with
Hi all,
Currently there are a number of different operators for dealing with optionals
that cover most of the use cases. However, I think I’ve identified a missing
complement for the existing operators for optionals.
Take the following outcomes for interacting with an optional using existing
o
