We intentionally decided to inline even bigger constants, because zip is really good at compressing them.
We will run more tests to make sure that this assumption still holds.

Added Optimization label.

The literal will be interpreted by JavaScript as a double, so only ~17 digit are needed to get the same bit pattern.

There is something more serious going on here, which causes erroneous constant folding in interpolation:

main() {
  print('${double.MAX_FINITE}');
  print('${[double.MAX_FINITE]}');
}

--->
  main: function() {
    P.print("179769313486231570814527423731704356798070567525844996598917476803157260780028538760589558632766878171540458953514382464234321326889464182768467546703537516986049910576551282076245490090389328944075868508455133942304583236903222948165808559332123348274797826204144723168738177180919299881250404026184124858368");
    P.print(H.S([179769313486231570814527423731704356798070567525844996598917476803157260780028538760589558632766878171540458953514382464234321326889464182768467546703537516986049910576551282076245490090389328944075868508455133942304583236903222948165808559332123348274797826204144723168738177180919299881250404026184124858368]));
  }

===>
179769313486231570814527423731704356798070567525844996598917476803157260780028538760589558632766878171540458953514382464234321326889464182768467546703537516986049910576551282076245490090389328944075868508455133942304583236903222948165808559332123348274797826204144723168738177180919299881250404026184124858368
[1.7976931348623157e+308]

The HConstant has type [subclass=JSPositiveInt], which seems wrong.
I guess the value does satisfy x == Math.floor(x)
But the form of the literal is clearly double:

    static const double MAX_FINITE = 1.7976931348623157e+308;

Another example:

   print('${1000000 * 1000000 * 1000000 * 1000000}');

--->
    P.print("999999999999999983222784");

===>
999999999999999983222784

Removed Type-Enhancement, Priority-Unassigned labels.
Added Type-Defect, Priority-High labels.
Changed the title to: "Incorrect teat[Inlining interferes with minification]".

Changed the title to: "Incorrect treatment of constants [was: Inlining interferes with minification]".

I agree that we should use exponential representations for integers that are too big.

I disagree with your assessment that this is a defect. The form of the literal doesn't have any influence on its value and for dart2js we just say that x == Math.floor(x) implies that x is an integer. After all we also say that 1.0 is an integer.

Removed Type-Defect, Priority-High labels.
Added Type-Enhancement, Priority-Medium labels.

I split out the constant-folding issue into issue #18103

Fixed in r43913.

Added Fixed label.