fix: The precision loss issue of new BigDecimal(double/float)

[qzmer1104]

new BigDecimal(double/float) can have precision issues because double is based on the IEEE 754 floating-point standard. It uses binary floating-point representation, and some decimal numbers cannot be represented exactly in binary, leading to precision errors.

[qzmer1104]

        BigDecimal v1 = BigDecimal.valueOf(0.1).add(BigDecimal.valueOf(0.2));
        BigDecimal v2 = new BigDecimal(0.1).add(new BigDecimal(0.2));
        System.out.println(v1);
        System.out.println(v2);
        System.out.println(v1.compareTo(v2) == 0);

And you'll get

0.3
0.3000000000000000166533453693773481063544750213623046875
false