Incorrect type-test of Infinity and NaN

[DartBot]

This issue was originally filed by olov.l...@gmail.com

---

~/projects/dart % cat nan_inf_type.dart
main() {
  var inf = double.INFINITY;
  var nan = double.NAN;
  print("$inf is int: ${inf is int}, is double: ${inf is double}, is num: ${inf is num}");
  print("$nan is int: ${nan is int}, is double: ${nan is double}, is num: ${nan is num}");
}

~/projects/dart % dart nan_inf_type.dart
Infinity is int: false, is double: true, is num: true
NaN is int: false, is double: true, is num: true

~/projects/dart % dart/frog/frogsh nan_inf_type.dart
Infinity is int: true, is double: true, is num: true
NaN is int: true, is double: true, is num: true

Frog and dartc should match the vm, i.e. Infinity and NaN is! int.

[DartBot]

This comment was originally written by drfibonacci@google.com

---

Added Area-Compiler, Triaged labels.

[DartBot]

This comment was originally written by zundel@google.com

---

These are runtime decisions made by trying to determine the dart type of a JS Number. Shouldn't affect dartc static analysis since code generation is removed. Unassigning from dartc as the other JS compilers likely have the same issue.

---

Removed Area-Compiler label.
Added New label.

[anders-sandholm]

Added Area-Dart2JS, Triaged labels.

[kasperl]

Changed the title to: "Incorrect type-test of Infinity and NaN".

[kasperl]

We do not treat infinity and NaN as ints in dart2js.

---

Added Fixed label.