I've reread my existing code. Ternary is very convenient but I'd vote
for either leaving it alone completely or find a Swift-y alternative
that enforces ( )s around the options.
That said, I couldn't really find any place where a "ternary-like switch
expression" would help much.
On 4/1/16 20:59 , firstname.lastname@example.org wrote:
Date: Mon, 4 Jan 2016 17:03:54 -0600
From: Matthew Johnson <email@example.com>
To: Paul Ossenbruggen <firstname.lastname@example.org>
> On Jan 4, 2016, at 2:37 PM, Paul Ossenbruggen via swift-evolution <email@example.com> wrote:
> Good feedback, I am all for making it feel more like swift. Any ideas would be welcome. I will also try to come up with some myself.
My suggestion is to leave ternary alone and try to come up with a ternary-like switch expression that is workable. I think that is likely the best change possible at this point.