== null is not a crime

[jshint]

== null is not a crime

[paulirish]

Totally agree. I think Anton just hadn't gotten around to this one before launch.

We'll get it in soon.

[devinus]

Just FYI, using obj === undefined || obj === null is actually faster in most JS engines than obj == null. But, in general I agree that obj == null is perfectly fine.

[Raynos]

Having code which checks for both undefined & null is bad. Your code should not be using null & undefined interchangeably.

This should be re factored so split the logical meaning of a variable being null or a variable being undefined in your code.

The only use case of it is when writing libraries to be used by others, so we don't expect them to split the logical meaning of null and undefined (which no-one does but everyone should).

[GarrettS]

Call me a sinner; I;ve used == null is for params. I'm w/PI on this one.

[valueof]

Don't mark == null as a poor relation when boss:true (closed by 4dbf400)

[valueof]

I've added support for == null when boss:true (4dbf400). Closing the ticket but feel free to comment the changeset.

[amigrave]

Additionally, I would allow the usage of extra parenthesis to suppress warning even if boss is not true.

Note that's in the description for the boss option at this url
http://www.jshint.com/docs/options/#boss

You can silence this error on a per-use basis by surrounding the assignment with parenthesis, such as:
for (var i = 0, person; (person = people[i]); i++) {}

IMHO should be the same for the == null

[Flimm]

I agree with amigrave's comment, so I converted it to issue #2456 .