Re: [swift-evolution] Nil-rejection operator

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

Re: [swift-evolution] Nil-rejection operator

t; > } catch ... > > It might even make 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 =

Re: [swift-evolution] Nil-rejection operator

-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 <br...@architechies.com> wrote: > >> On Feb 8, 2017, at 12:00 PM, Jack

Re: [swift-evolution] Nil-rejection operator

find the concept interesting, I give a big -1 for using the ‘!’ > operator for something else that fatal error. > >> Le 8 févr. 2017 à 21:00, Jack Newcombe via swift-evolution >> <swift-evolution@swift.org <mailto:swift-evolution@swift.org>> a écrit : >> >>

Re: [swift-evolution] Nil-rejection operator

ig -1 for using the ‘!’ > operator for something else that fatal error. > >> Le 8 févr. 2017 à 21:00, Jack Newcombe via swift-evolution >> <swift-evolution@swift.org <mailto:swift-evolution@swift.org>> a écrit : >> >> Hi all, >> >

[swift-evolution] Nil-rejection operator

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