Indicate that "big ints" lead to unexpected results when compiled to JavaScript

[sethladd]

In A Tour of the Dart Language, the section on numbers contains an example of a big integer, but that code run on the Dartboard produces unexpected results:

main() {
  var bigInt = 3465346583465243765923847659234765928347659567398475647495873984572947593470294387093493456870849216348723763945678236420938467345762304958724596873045876234572037862934765294365243652548673456705673465273465246734506873456729457623845623456234650457693475603768922346728346256;
  print(bigInt);
}

output:
3.465346583465244e+276

I know the reason for this, but considering that there's a tip at the top of the page to try the examples out on Dartboard, shouldn't the section on integers mention the different behavior of ints on the VM vs compiled to Javascript?

[kwalrath]

Also reflect (here and elsewhere) that people should generally use num or int if they want a numeric type, not double. From Bob Nystrom:

In my code, I either want two kinds of numbers:

1. Only integers with no floating points (like when I'm going to use them for list indices).
2. Any number including floating points.

"int" handles the first, and "num" handles the second. I can't think of any time where I would want a number that must have a floating point and cannot be an integer, which is what "double" expresses.

[sethladd]

There is a note in the language tour about the differences between VM and JS handling of big integers.

---

Added Fixed label.

[nicolasgarnier]

This issue has been moved to Github as part of a migration. Please use the Issue on Github going forward: https://github.com/dart-lang/dartlang.org/issues