Any way that ToShortest could have functionality for max requested precision? about double-conversion HOT 2 CLOSED

I guess another alternative to having ToShortest somehow take in requested digits, would be to have another flag for ToPrecision. Something like TRIM_SIGNIFICANT_ZEROES_AFTER_POINT

So that tests like this could pass when added to TEST(DoubleToPrecision)

  builder.Reset();
  CHECK(dc8.ToPrecision(2000, 6, &builder));
  CHECK_EQ("2000", builder.Finalize());

  builder.Reset();
  CHECK(dc8.ToPrecision(2000.001, 6, &builder));
  CHECK_EQ("2000", builder.Finalize());

So even though I requested 6 digits, if its nothing but zeroes after the point I would rather they be trimmed away. I guess I initially expected that not setting either of EMIT_TRAILING_DECIMAL_POINT
or EMIT_TRAILING_ZERO_AFTER_POINT would behave in this way, but now I understand those only matter if the decimal point occurs after the requested digits.

from double-conversion.

I can see your point, but I don't think this functionality is used often enough to add it to the library. (Especially, because it's quite easy to just fix the output after the fact).

I'm quite busy these days, so I rather just close this issue, instead of giving the hope that it might happen anytime soon.

from double-conversion.