Control structure conditional:
- verbose
- boring
- may result to nothing
Ternary expression:
- terse
- all action
- always leads to a result
Submitted 2 days ago by guber@lemmy.blahaj.zone to [deleted]
https://lemmy.blahaj.zone/pictrs/image/4162679e-4107-4971-9740-1c5b5cd9adaf.webp
Control structure conditional:
Ternary expression:
Don’t you just love the readability
a = a > b ? (b > c ? (a < d ? c : a) : d) : (b < c ? a : d )
Weird example. 3 nested conditionals is not the typical use case for a ternary, and 2 of the 5 branches result in a pointless a=a assignment. I agree this is bad code, but it’s just as bad and hard to parss in a normal if-else structure too:
if (a>b) { if (b>c) { if (a<d) { a=c; } else { a=a; } } else { a=d; } } else { if (b<c) { a=a; } else { a=d; } }
In another situation, though, it’s perfectly readable to have a much more typical ternary use case like:
a = c > d ? c : d
And a pair of parentheses never hurt readability either:
a = (c > d) ? c : d
this is way more nested ternary operators than I would ever use (which I understand is for the sake of example) but if you rearrange them so that the simplest statements are in the true branches, and use indentation, you can make it at least a little more readable
a = a <= b ?
(b < c ? a : d)
: b <= c ?
d
: (a < d ? c : a);
Bah
Ternary is just a compressed if-elseif-else chain with a guaranteed assignment.
If you format it like a sane person, or like you would an if/else chain, then it’s way easier to read than if/else chains.
if else chain? believe of or not, straight to jail.
Hey, when you gotta pick a value from a bunch of options, it’s either if/elseif/else, ternary, switch/case, or a map/dict.
Ternary generally has the easiest to read format of the options, unless you put it all on one line like a crazy person.
x = if y > 5 { "foo" } else { "bar" }
This is just superior to anything else
In what language is that valid syntax?
This is Rust syntax, but there’s similar syntax in Haskell
This is valid rust. I don’t know if there are more languages with this feature
I honestly can’t see how this is more readable than
x = (y > 5) ? “foo” : “bar”
I get that it’s a syntax that needs to be learned, but it’s just so clean and concise!
Because it can be done for multiple lines too. And you can do else-if too. Also, “if” and “else” is more recognizable than “?” and “:”
x = if y > 5 { println!("Y was over 5"); z + 5 } else if y < 0 { handle_negative_y(y); z - y } else { println!("<WARN> unexpected value for y"} 0 }
What I like about using if
and else
for that is that you’re already using those keywords for branching in other parts of the code.
Though my least favorite is probably Python’s:
x = "foo" if y > 5 else "bar"
It just seems backwards to me
Never forget your roots
(setq x (if (> y 5) :foo :bar))
(‘bar’,:‘foo’)&({~ 5&< )
I love ternary for assigning to constants.
At my previous workplace we had a C macro that was something like
#define CheckWhatever(x__, true__, false__) \ whatever(x) ? (true__) : (false__)
I don’t remember this shit, so I’m just paraphrasing cursed C. The question one would ask is… why? Well, because you also want to do
#define CheckWhatever2(x__, true__, false__) \ CheckWhatever((x__ ##1), (true__), (false__)) \ CheckWhatever((x__ ##2), (true__), (false__))
And, of course
#define CheckWhatever3(x__, true__, false__) \ CheckWhatever2((x__ ##1), (true__), (false__)) \ CheckWhatever2((x__ ##2), (true__), (false__))
yeah… yikes. c is a beautiful language but thing like these are why macros may be it’s largest blemish. hope that codebase doesn’t keep planes flying!
For it’s faults, I think what makes C beautiful is that it gives you complete freedom do be an absolute idiot.
Whenever I decide to hack something together with an arcane macro, I feel like an animal being released back into the wild, with the compiler yelling “Be free! Explore the mysteries of our incomprehensible world!”
Easily solved by using Rust and have literally anything evaluate your expression and return whatever
All my homies love ternary
you would love jsx/tsx with react
“Brought to you by the Go gang”
A lot of languages have more intuitive ternary syntax than C
infinitesunrise@slrpnk.net 2 days ago
For real though I actually find them incredibly useful for creating clean and readable code. I wish Lua 5.1 had a ternary syntax.
p_consti@lemmy.world 2 days ago
Ternary, and inline switch (match expressions), as found in functional languages
infinitesunrise@slrpnk.net 1 day ago
Oh god yea, replicating switch functionality with a huge column of elifs is so gross.
nimpnin@sopuli.xyz 1 day ago
I’ve survived 11 years of programming without ternary operators and prefer to keep it that way
lime@feddit.nu 1 day ago
luas operators are all text in order to be readable. more symbols makes code less readable.
if you want a one line operation that gives a default result, use
or
:local a = b or c
is equivalent toif b then a = b else a = c end
.kuberoot@discuss.tchncs.de 1 day ago
The issue with Lua’s and/or in this context is that they don’t work if false or nil are valid values. In
a and b or c
, ifb = false
, the result is alwaysc
.I also love null-related operators like ?? and ?. for this, since they explicitly check for null, letting you handle any non-null values for optional/default values. The syntax can get a bit cursed, like
maybeNull?.maybeMethod?.(args)
in JS, but I still prefer that to writing out multiple field accesses in an if condition… And arguably the code is only less readable if you aren’t acclimated to it.All that said I do really appreciate Lua’s simplicity, as a language that provides tooling to create the features you want instead of building them into the language, though I wish it had some conventional regex instead of its own patterns.
infinitesunrise@slrpnk.net 1 day ago
OK true, technically speaking it is indeed more readable, I guess I really meant that it takes far longer to read. I do admire Lua’s barebones simplicity.