43
you are viewing a single comment's thread
view the rest of the comments
[-] julianh@lemm.ee 7 points 3 years ago

Ok some of these I understand but what the fuck. Why.

[-] RagingToad@feddit.nl 8 points 3 years ago

I'm not sure if you really want to know, but:

greater than, smaller than, will cast the type so it will be 0>0 which is false, ofcourse. 0>=0 is true.

Now == will first compare types, they are different types so it's false.

Also I'm a JavaScript Dev and if I ever see someone I work with use these kind of hacks I'm never working together with them again unless they apologize a lot and wash their dirty typing hands with.. acid? :-)

[-] hstde@lemmy.fmhy.ml 1 points 3 years ago

Not a JavaScript dev here, but I work with it. Doesn't "==" do type coercion, though? Isn't that why "===" exists?

As far as I know the operators ">=" and "<=" are implemented as the negation of "<" and ">" respectively. Why: because when you are working with sticky ordered sets, like natural numbers, those operators work.

Thus "0<=0" -> "!(0>0)" -> "!(false)" -> "true"

Correct me if my thinking is wrong though.

[-] Daniikk1012@lemmy.world 1 points 3 years ago

a >= b, is equivalent to, !(a < b)

this post was submitted on 16 Jun 2023
43 points (93.9% liked)

Programmer Humor

44155 readers
7 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 7 years ago
MODERATORS