https://linen.dev logo
Powered by
# haxe-ui
  • b
    well, suffice to say, im certainly ok with NOT using == true / false...
  • a
    that's okay
  • a
    it's your code, do as you want
  • b
    ah wait, i got it
  • b
    but im NOT into changing 500 instances of it over 100 files... 😄
  • a
    i don't think it matters either way
  • a
    at the end of the day, if it works... it works
  • b
    this behaves differently
  • a
    compiler team seems to believe there's value to it as well
  • a
    otherwise they'd probably just wipe it from the output
  • a
  • b
    but that doesnt change anything with !bool or bool == false, thats just inconsistency?
  • a
    bool is null and not true
  • b
    !bool is the same between targets it seems
  • b
    right, but im saying the same inconsistency is there with !bool?
  • a
    but the else captures 2 states instead of the "normal" 2 states
  • b
    no, with 
    !bool
    both return false
  • b
    yikes
  • b
    i'm confusing myself tbh
  • b
    me too
  • a
    it doesn't if you don't have anything to process on a boolean that's specified as null
  • a
    cause if a bool is set to null instead of false, that might actually mean something has gone wrong somewhere 😂
  • b
    anyways, imma go to bed and pretend this conversation never happened. Night chaps 🙂
  • b
    i guess that means == false is the problem??
  • b
    sounds that way 😮
  • b
    or wait... I'm really confused now x)
  • b
    anyways, goodnight, i think we can all agree this conversation never happened...
  • a
    basically, it's just js funkiness to watch out for and we should probably forget
  • a
    gnight
  • b
    dynamic null value on javascript:
1...101610171018...1687Latest