this post was submitted on 08 Jul 2023
136 points (93.0% liked)

Programmer Humor

19589 readers
589 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 1 year ago
MODERATORS
Feyter@programming.dev
anzo@programming.dev
BurningTurtle@programming.dev
pylapp@programming.dev
136
I don't want to use ternaries (lemmy.xylight.dev)
submitted 1 year ago by Xylight@lemmy.xylight.dev to c/programmer_humor@programming.dev
20 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] orowith2os@beehaw.org 9 points 1 year ago* (last edited 1 year ago) (1 children)

The whole idea of expressions is very nice, and I can't imagine using ternary expressions anywhere after learning Rust.

Also implicit returns ❤️

[–] msage@programming.dev 1 points 1 year ago (2 children)

I never got to like implicit anything.

Not even returns. Ever.

[–] pomodoro_longbreak@sh.itjust.works 1 points 1 year ago

You get used to it pretty quickly. After a while you wonder how you ever lives without it. Explicit returns feel like ending an if with endif. The end of the conditional's scope is implied by the end of the block by } or whatever.

[–] orowith2os@beehaw.org 1 points 1 year ago

Doing everything explicitly can get to be annoying, especially when it comes to what you had to do before without Vulkan's VK_EXT_shader_object.

It's clear that some stuff should be implicit - most types in programming languages, for example; needing to specify a struct type and then the struct itself can be annoying - and other stuff explicit, like low level operations.

Returns are something that usually fall into that "implicit" category. Why should I do let a = function(); return a; when I can just do function()? It's shorter, simpler, and I don't waste keystrokes.