87
Avoiding if-else Hell: The Functional Style
(lackofimagination.org)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 24 Sep 2024
87 points (92.2% liked)
Programming
17314 readers
27 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
It has conditionals not but actual if statements. Not really different in functionality but a more consistent style.
They’re still ifs. They’ve just been lambda’d and assigned to constants.
branching ≠ if ≠ conditional
They're all related but can't just be used interchangeably. "if" is a reserved keyword to indicate a specific syntax is expected. It's not the semantics the author was trying to change, it's the syntax, and the overall point is that you aren't always required to use the specific "if" syntax to write code just like you're not required to use "while" to achieve looping.
If you decompile that code you won’t get lambdas. You get ifs. Because that is how the hardware is build. Ifs/ands/Ors that is what computing is built on. Everything else is flavor.
The title of the post is "how to avoid if-else hell", not "how to avoid conditionals". Not sure what's your point.