To answer your meta question, no, we don’t want to add lots of operators. We
are willing to add them if they are very strongly motivated, but prefer not to
if there are other ways to solve the problem.
In this case it sounds like:
x = optionalValue ?? x
Is a reasonable substitute.
-Chris
possibly off-topic but what i would really find useful is some way of
expressing guard/if assignment instead of initialization so that
let geomSource:UnsafeMutableBufferPointer?
if let geometryFile:String = geometryFile
{
guard let _geomSource:UnsafeMutableBuffe
Ah, sorry, I misread! For readability I think I'd still favor something like:
if let b = b {
dict[a] = b
}
And I think some the arguments made in #0024 may still apply here, though feel
free to discuss!
Stephen
> On Dec 21, 2017, at 1:37 PM, Benoit Pereira da silva wrote:
>
> S
Stephen,
You are right the proposal #0024 is very close.
But in fact the logic is inverted.
When using «=? » the right item is optional.
a =? b assigns « b » to « a » only if « b » is defined.
So if an optional is defined =? will not erase its value.
But my real questions was…
Do you have s
Such an operator was proposed here:
https://github.com/apple/swift-evolution/blob/60a8980a66a0a1341871ec323797c5547d0e0925/proposals/0024-optional-value-setter.md
It was ultimately rejected:
https://lists.swift.org/pipermail/swift-evolution-announce/2016-February/43.html
Stephen
> On Dec 2
Dear all,
That’s not ambitious but i think worth be explored.
What do you think for example of this Infix operator?
« =? » allows to express optional assignments in a very concise way.
// The `=? operator allows simplify optional assignements :
// `a = b ?? a` can be written : `a =? b`
infix
