Aijan@programming.dev to Programming@programming.dev · 1 month agoSelf-documenting Codelackofimagination.orgexternal-linkmessage-square72fedilinkarrow-up1101arrow-down116cross-posted to: hackernews
arrow-up185arrow-down1external-linkSelf-documenting Codelackofimagination.orgAijan@programming.dev to Programming@programming.dev · 1 month agomessage-square72fedilinkcross-posted to: hackernews
minus-squaretraches@sh.itjust.workslinkfedilinkEnglisharrow-up48arrow-down1·1 month agoAgreed. OP was doing well until they replaced the if statements with ‚function call || throw error’. That’s still an if statement, but obfuscated.
minus-squareBrianTheeBiscuiteer@lemmy.worldlinkfedilinkarrow-up7·1 month agoDon’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”.
minus-squarerooster_butt@lemm.eelinkfedilinkarrow-up3·1 month agoShort 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.
Agreed. OP was doing well until they replaced the if statements with ‚function call || throw error’. That’s still an if statement, but obfuscated.
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”.Short circuiting conditions is important. Mainly for things such as:
Without short circuit evaluation you end up with a null pointer exception.