this post was submitted on 21 Oct 2024
85 points (86.3% liked)

Programming

17416 readers
79 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
you are viewing a single comment's thread
view the rest of the comments
[–] traches@sh.itjust.works 47 points 3 weeks ago (1 children)

Agreed. OP was doing well until they replaced the if statements with ‚function call || throw error’. That’s still an if statement, but obfuscated.

[–] BrianTheeBiscuiteer@lemmy.world 7 points 3 weeks ago (1 children)

Don't mind the || but I do agree if you're validating an input you'd best find all issues at once instead of "first rule wins".

[–] rooster_butt@lemm.ee 3 points 3 weeks ago

Short circuiting conditions is important. Mainly for things such as:

if(Object != Null && Object.HasThing) ...

Without short circuit evaluation you end up with a null pointer exception.