▲ 115 ▼ The JavaScript type coercion algorithm (lemmy.ml) submitted 1 year ago by sleeplessone@lemmy.ml to c/programmerhumor@lemmy.ml 37 comments fedilink hide all child comments
[–] Mr_Fish@lemmy.world 17 points 1 year ago (2 children) To make it even worse permalink fedilink source hideshow 2 child comments replies: [–] Telemachus93@slrpnk.net 14 points 1 year ago Mh, '0' is a nonempty string, so !'0' returns false. Then of course !(!'0') would return true. I'd absolutely expect this, Python does the same. And the second thing is just JavaScript's type coercion shenanigans. In Python bool('0') # returns True because of nonempty string bool(int('0')) # returns False because 0 == False Knowing that JavaScript does a lot of implicit type conversions, stuff like that doesn't strike me as very surprising. permalink fedilink source parent [–] lime@feddit.nu 3 points 1 year ago wait hang on... permalink fedilink source parent
[–] Telemachus93@slrpnk.net 14 points 1 year ago Mh, '0' is a nonempty string, so !'0' returns false. Then of course !(!'0') would return true. I'd absolutely expect this, Python does the same. And the second thing is just JavaScript's type coercion shenanigans. In Python bool('0') # returns True because of nonempty string bool(int('0')) # returns False because 0 == False Knowing that JavaScript does a lot of implicit type conversions, stuff like that doesn't strike me as very surprising. permalink fedilink source parent
