Custom Precision on floating point numbers

[DarkZeros]

When storing floating point values, exact representation is not possible.
ie: -0.2 -> -0.019999995827674866

However, when precision is not a big issue this introduces huge about of bloat in the JSON file. So there should be an option to specify how many characters of precision. Like it is possible in std::ostringstream (std::ostreams), and in printf.

Currently these 2 methods would be desired:

json j;
j["float"] = -0.123;
j.precision(2);
cout << j;

json j;
j["float"] = -0.123;
j.precision(2);
printf("%s", j.dump().c_str());

Desired: {"float":-0.12}
Currently: {"float":-0.12300000339746475}

[gregmarr]

#1121

[nlohmann]

Workaround: #1191

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[shubhdev]

FWIW, I feel this feature would be great as well . The workaround is a bit ugly, and I am not sure it will always work. #1121 seems to have gone stale unfortunately 😞

[lrasku]

Regarding the workaround, the old, prettier workaround described in #768 comments stopped working due to the new Grisu2 algorithm, which is selected on platforms that implement IEEE-754 floating points, i.e. almost all of them. The old workaround works if you disable the platform check, i.e. patch static constexpr bool is_ieee_single_or_double = false; in dump_float(number_float_t x).

[dvjdjvu]

round((int)(val_double * 10)) / 10;
for 1 digit after ,

[gregmarr]

@dvjdjvu That only works if that number can be represented exactly by a double. Some very surprising numbers can't, such as 0.1. It is actually stored as something like 1.00000000000000005551115123126e-1

[maddanio]

why did this get closed? I would say this is a bug, since the library simply ignores the precision setting of the stream it is writing to.

[maddanio]

I really want this to work properly (we dont need 10 places after the dot and it wastes a lot of space) and will submit a pr later

[maddanio]

stale bot closed as "completed"? wow, now we complete issues by letting them go stale :-D. anyhow, i know this is open source and we didnt pay for this, so if we want this I will implement it, l8er :)

[nlohmann]

I would be glad to see a PR

[maddanio]

I have something working. it is not 100% backward compatible though, since for dumping to an ostream it takes the precision parameter of the ostream as a precision, which defaults to 6. now it can probably be more. I personally think 6 is enough for any realistic use case, but your mileage may vary. if you don't want to accept that then i dont know how to parameterize it for ostream dumping. well, unless you want to set it on the json itself, or you could make some fancy wrapper i.e. os << with_precision(my_json_value, n).
of course some tests fail now with this, due to the precision change, so I will hold back on the pr until a decision is reached on this. see my commit here

[t-b]

it is not 100% backward compatible though

I'm not one of developers here, but I think only 100% backwards compatible solutions will be accepted.