x27;s a change that might be worthwhile (but without breaking
backwards compatbility of course), especially considering the original
issue, which was a precision loss when converting float to big decimal
through valueOf.
pt., 24 sty 2025 o 12:11 Jan Kowalski napisał(a):
> Thank you all
Thank you all for your replies!
I'm aware of the workaround (we are using this approach in our project) and
the problematic issues with decimal conversions. However, I also think that
we should make sure that the behaviour of the code is more predictable. For
me and other developers, it might be c
Hi!
I’m currently working on a project that heavily relies on float values, and
we occasionally use BigDecimal for more precise mathematical operations.
However, I’ve noticed that the current BigDecimal constructor
implementation only supports double, which can lead to unintentional type
conversio
