orhtej2@eviltoast.org to Programmer Humor@programming.devEnglish · 1 day agoPeak code reuseeviltoast.orgimagemessage-square41fedilinkarrow-up1440arrow-down15
arrow-up1435arrow-down1imagePeak code reuseeviltoast.orgorhtej2@eviltoast.org to Programmer Humor@programming.devEnglish · 1 day agomessage-square41fedilink
minus-squarebobo@lemmy.mllinkfedilinkarrow-up7·edit-26 hours ago in a dynamic typed language with dumb string to int coercions, I kinda get why such a would library exists. If string return nan, else % 2 So it’s more a symptom of terrible language design than modern dependency hell. Dependency chain: is-even depends on is-odd which depends on is-number
minus-squareDecq@lemmy.worldlinkfedilinkarrow-up2arrow-down1·edit-25 hours ago If string return nan, else % 2 So now you return a number type if it’s a string and a boolean if it’s an integer. How does that make sense? The is-even lib exists to sanitize input by throwing an exception which imho is better. Edit: having looked at the code better. Apparently it still allows string coercion (boo). It only checks for non integer numbers.
minus-squarebobo@lemmy.mllinkfedilinkarrow-up1·4 hours agoGood point, but you can do if === true… and else if === false… But definitely better to throw an error instead of nan.
If string return nan, else % 2
Dependency chain: is-even depends on is-odd which depends on is-number
So now you return a number type if it’s a string and a boolean if it’s an integer. How does that make sense?
The is-even lib exists to sanitize input by throwing an exception which imho is better.
Edit: having looked at the code better. Apparently it still allows string coercion (boo). It only checks for non integer numbers.
Good point, but you can do if === true… and else if === false…
But definitely better to throw an error instead of nan.
deleted by creator