If you try this var_export(2.1245) returns "2.1245". It is right.

Thank you for taking the time to write to us, but this is not
a bug. Please double-check the documentation available at
http://www.php.net/manual/ and the instructions on how to report
a bug at http://bugs.php.net/how-to-report.php

A float(1.0) is stored as a float(1) (it's the same), so var_export(1.0) outputs 1.

($a === eval('return ' . var_export($a, true) . ';')) should result in true for any given $a. "1" isn't a correct representation of float(1) as it results in int(1).

Not sure if this is the same problem

http://3v4l.org/ZRPXO

var_export(5.3); echo "\n";
var_dump(5.3); echo "\n";

outputs:
5.29999999999999982236432
float(5.3)

in this case luckily 5.29999999999999982236432 == 5.3, and it pass ($a === eval('return ' . var_export($a, true) . ';')) definition
but i give this example to show that var_dump is better (looking) than var_export on double value

so please take it seriously

Thank you for your bug report. This issue has already been fixed
in the latest released version of PHP, which you can download at 
http://www.php.net/downloads.php

Fixed in 7.0.2. Unfortunately, I screwed up the fix, creating bug #71314.

I think, that Reflection should also use this new logic for exporting float numbers: check https://3v4l.org/2JFbL

This will be consistent with current var_export behavior.

That sounds like a good idea, maybe it should be a separate bug report.