@[email protected] to [email protected] • 3 months agoSelf-documenting Codelackofimagination.orgexternal-linkmessage-square63fedilinkarrow-up1101arrow-down117cross-posted to: [email protected]
arrow-up184arrow-down1external-linkSelf-documenting Codelackofimagination.org@[email protected] to [email protected] • 3 months agomessage-square63fedilinkcross-posted to: [email protected]
minus-square@[email protected]linkfedilinkEnglish47•3 months 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-square@BrianTheeBiscuiteerlink7•3 months 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-square@[email protected]linkfedilink3•3 months 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.