Haxe

well it took me 5 minutes for like 10 files

you can even add it to the haxeui codebase so that everyone who opens the project will adopt the specified code style

i'd never use == true, but also i would never use implicit bool conversions for non bool types bc i find that evil x)

anyway, ill close the PR and stick to documenting lol

i think thats where it comes from, js, i think maybe i feel like haxe is like js

but it _feels_ like it so "if (x)" feels "dangerous"

~~haxe treats `if (foo)` differently on js target than cpp target :3~~

~~i think it's an artefact from the fact that most languages are based on C, which used to not have bool types so most things could be converted to a bool~~ nvm i get what you mean now, yes you're right it probably does come from js

```hx
var bool:Null<Bool> = null;
if (bool == false) {
  trace("hey");
}
```

!run var bool:Null<Bool> = null;
if (bool == false) {
  trace("hey");
}

oh as in false == null gets evaluated differently??

doesn't work as i expect it does, but there's definitely something haxe does differently for js here

having trouble recalling, will experiment a bit

ive always thought my use of "==true" was irrational, but maybe there is something

i know static targets can't set primitive values to null

as i said, id never use it in java or, c++ where im _sure_ it cant be misunderstood