dartc is too permissive of null operands (checked mode)

[DartBot]

This issue was originally filed by [email protected]

---

Two examples of many:

main() {
  Expect.throws(() { print(1 < null); }); // dartc: false
  Expect.throws(() { print(1 - null); }); // dartc: NaN
}

=> Expect.throws() fails

[DartBot]

This comment was originally written by [email protected]

---

Added Area-Compiler, Triaged labels.

[DartBot]

This comment was originally written by [email protected]

---

Leaving open. The question is about code generation issues, but static analysis could provide a warning in this case (using null in a boolean expression)

[kasperl]

Removed Area-Compiler label.
Added Area-Analyzer label.

[bwilkerson]

Added this to the Later milestone.

[bwilkerson]

Removed this from the Later milestone.
Added this to the M3 milestone.

[bwilkerson]

Removed this from the M3 milestone.
Added this to the M4 milestone.

[bwilkerson]

dartc has been deprecated in favor of the new analysis engine, and neither generate code anymore.

---

Added WontFix label.

[clayberg]

Removed this from the M4 milestone.
Added this to the M5 milestone.