You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are challenges when using BigDecimal and constructors such as BigDecimal(Double)vsBigDecimal(String). For example: BigDecimal(1.0) has different "scale" than BigDecimal("1.0")
Design & implement a consistent policy for FloatingBigRational. Options may include:
Follow the patterns of BigDecimal
Always show a decimal point to emphasize the floating-point nature, eg, "3.0 / 2.0" vs "3 / 2"
Present code leans towards the former (partly by accident).
The text was updated successfully, but these errors were encountered:
There are challenges when using
BigDecimal
and constructors such asBigDecimal(Double)
vsBigDecimal(String)
. For example:BigDecimal(1.0)
has different "scale" thanBigDecimal("1.0")
Design & implement a consistent policy for
FloatingBigRational
. Options may include:BigDecimal
Present code leans towards the former (partly by accident).
The text was updated successfully, but these errors were encountered: