Conversation

Notices

1. ~/phranck (phranck@chaos.social)'s status on Tuesday, 13-Jun-2023 20:45:14 JST ~/phranck

   The ternary operator is a very handy notation to simply abbreviate if else constructs. And often it’s seen nested - one, two or three times. The compiler has no problems with such code. But we, as human beings, reach the limits.

   I wrote a short article about it:
   https://woodbytes.me/en/blog/don-t-use-nested-ternary-operators-in-swift

   #Swift #SwiftUI #SwiftLang #iOSDev #MacDev

   // @swiftui @swift

   • Aral Balkan (aral@mastodon.ar.al)'s status on Tuesday, 13-Jun-2023 20:45:07 JST Aral Balkan

     in reply to

     @phranck @swiftui Agree; was the reason I added if/then/else to Kitten templates (https://codeberg.org/kitten/app#conditionals).

     But the big caveat with wrapper functions is they don’t short circuit. So not only the conditional but every branch gets evaluated. Which is not what happens with the built-in ternary operator and can lead to crashes if you expect branches to only evaluate when true and for values to exist when branches are evaluated. So you have to use optional chaining everywhere.

   • Aral Balkan (aral@mastodon.ar.al)'s status on Tuesday, 13-Jun-2023 21:13:02 JST Aral Balkan

     in reply to

     • lksz :yayblob:

     @phranck @swiftui @lksz Yeah, wrapping the branches in a closure would avoid the issue and having a magic compiler directive in Swift helps :) Sadly, not a solution I can use in Kitten with tagged template strings in JavaScript. (At least not without making the syntax even worse than what it would be with simply using the ternary operator within string interpolations.)

   • ~/phranck (phranck@chaos.social)'s status on Tuesday, 13-Jun-2023 21:13:03 JST ~/phranck

     in reply to

     • Aral Balkan
     • lksz :yayblob:

     @aral @swiftui Nope, the @autoclosure addition by @lksz prevents evaluation of all branches. Check out the code (and test it in a playground).

     https://chaos.social/@lksz/110536451857805701