Skip to content

BigDecimal API changes and bugfixes
Compare
Choose a tag to compare
@ionspin ionspin released this 17 Apr 10:41
0.3.0
939d631
  • Fixed losing scale when there is a carry in addition in BigDecimal.
  • Fixed BigInteger numberOfDecimalDigits which would return 0 for 0 instead of 1.
  • Fixed #168 - Fix invalid rounding results Development roadmap for version 0.3.0 states 'API statbilization' so:
  • API CHANGE Extensions functions used to create BigDecimal from primitive types have been split into 'toBigDecimal(exponentModifier...)' and 'toBigDecimalUsingSignificandAndExponent(exponent...)' to bring more clarity to the API and solve #164
  • API CHANGE BigInteger uses a sum of magnitude elements as part of hash code instead of array hash code as it wasn't stable on JS
  • API CHANGE BigDecimal hashCode doesn't include decimal mode anymore, so it respects contract that hash code equals another hash code when equals returns true.
  • API CHANGE BigDecimal equals doesn't consider decimal mode anymore. Two big decimals are now equal only if they represent the same number.
  • Fixed decimal mode precision/scale mismatch in BigDecimal #161
    • NOTE: API CHANGE final precision is now desiredPrecision + scale
  • Add @SharedImmutable to BigInteger to support native multithreading #159
Assets 2
Loading