All Versions
27
Latest Version
Avg Release Cycle
36 days
Latest Release
-

Changelog History
Page 1

  • v0.3.4-SNAPSHOT Changes

    • 👻 Throw a specific exception when exponentiation of zero with negative exponent is attempted (#206)
    • ✂ Remove zero counting debug log (#210)
    • 🛠 Fix for invalid decimal precision when dividend has exponent -1 (#195)
    • API CHANGE Narrowing function (longValue, intValue, doubleValue...) are now defaulting to exactRequired which means they will throw ArithmeticException if the conversion cannot be done without loss.
    • 🚀 Use temporary javascript comparison workaround to handle precision loss. This is fixed in kotlin 1.6.20 and the workaround will be removed once that is released.

  • v0.3.3 Changes

    • ➕ Add support for apple silicon (#188 #194)

  • v0.3.2 Changes

    • ➕ Added kotlinx serialization support library
    • Enabled gradle dependencies verification (bootstrapped)
    • 🛠 Fix for losing decimal mode when using unary minus (#184)
    • 🛠 Fix for losing sign when narrowing to long from big integer (#186)

  • v0.3.1 Changes

    • 🛠 Fix for #176, a case of unclear API. Methods roundToDigitPositionAfterDecimalPoint and roundToDigitPosition would set decimal precision to the number of digits present in the result after the rounding was completed. Now they only set decimal precision if it's explicitly set, otherwise it stays unlimited.
    • ⬆️ Bump to 1.5.0

  • v0.3.1-SNAPSHOT Changes

    • 🛠 Fix for #176, a case of unclear API. Methods roundToDigitPositionAfterDecimalPoint and roundToDigitPosition would set decimal precision to the number of digits present in the result after the rounding was completed. Now they only set decimal precision if it's explicitly set, otherwise it stays unlimited.
    • ⬆️ Bump to 1.5.0

  • v0.3.0 Changes

    • 🛠 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

  • v0.2.8 Changes

    • 🛠 Fixed support for watchosX64/watchos86 (#150)
    • 🛠 Fixed parsing characters outside of radix range (#152)
    • 🛠 Fixed invalid byte array intialization (#153)
    • 🛠 Fixed rounding KDoc (#156)

  • v0.2.7 Changes

    🚀 Same as 0.2.4 just a successful upload and release to Maven central

  • v0.2.5 Changes

    Failed uploads to maven central, don't use these versions. https://status.maven.org/incidents/z70skgbq8vgc

  • v0.2.4 Changes

    • ⬆️ Bump to kotlin 1.4.30
    • 🛠 Fix invalid to string when big decimal is zero (#148)
    • 🛠 Fix xor test which was previously testing bit shifting instead of xor (#147)
    • 🛠 Fix biginteger xor operands magnitude array length mismatch (#144)
    • 🛠 Fix biginteger bitwise operations sign (#142)
    • ➕ Added (back) support for legacy js target (#138)