num toString() output varies between Dartium and JS execution for whole number nums

[DartBot]

This issue was originally filed by mikeebe...@gmail.com

---

I am using Dart Editor Version 0.1.0.201208061534, Build 10315 with Dart SDK version 10311

If I use num.toString(), the output varies based on whether I am running my Dart program native (in Dartium) vs. running in FF/Chrome using the generated JS output by the Dart Editor. This variation in results only shows up for num values that have ZERO after the decimal (e.g., 10.0 - i.e., whole numbers). The JS code will truncate the ".0" in its output whereas the native Dartium output shows "10.0" as expected.

See attached test files. This seems like it will be an easy problem to resolve. thanks.

---

Attachments:
Dart-Num-Format-Differences-vs-JS.html (990 Bytes)
Num-Format-Test.dart (179 Bytes)

[iposva-google]

cc @floitschG.
Added Area-Library, Triaged labels.

[floitschG]

This is unfortunately very hard to solve. When compiling to JavaScript we currently merge integers and doubles. That is, in the JavaScript program we only have doubles.
Therefore we cannot know if 10 represents the double 10.0 or the integer 10.
When printing the number we have to guess what type the original value was, and our guess is integer. Unless we fix the integer/double merging we cannot do much better. If we printed the numbers as doubles we would get similar bug-reports for integers...
The correct number semantics is tracked in issue #1533.

---

Added Duplicate label.
Marked as being merged into #1533.