# \`BigInt\` status

**URL:** <https://forums.swift.org/t/bigint-status/65566>\
**Category:** Swift Numerics\
**Created:** [June 14, 2023, 6:32am UTC](https://forums.swift.org/t/bigint-status/65566 "2023-06-14T06:32:55Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![mgriebling](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/mgriebling/32/29936_2.png) [@mgriebling](https://forums.swift.org/u/mgriebling)\
**Post date:** [June 14, 2023, 6:32am UTC](https://forums.swift.org/t/bigint-status/65566/1 "2023-06-14T06:32:55Z")

</div>

Does anyone know when `BigInt` (in one of the subdirectories) would be released? As well is there a `BigDecimal` in the works somewhere. I'm aware of the GitHub project.

---

<div class="post-metadata">

**Author:** ![SylvanM](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/sylvanm/32/30432_2.png) [@SylvanM](https://forums.swift.org/u/SylvanM)\
**Post date:** [June 18, 2023, 2:20pm UTC](https://forums.swift.org/t/bigint-status/65566/2 "2023-06-18T14:20:50Z")

</div>

Is BigInt guaranteed to become part of the standard library?

---

<div class="post-metadata">

**Author:** ![mgriebling](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/mgriebling/32/29936_2.png) [@mgriebling](https://forums.swift.org/u/mgriebling)\
**Post date:** [June 18, 2023, 2:56pm UTC](https://forums.swift.org/t/bigint-status/65566/3 "2023-06-18T14:56:43Z")

</div>

At least initially it will likely be released as part of the Swift Numerics library. Sometime in the future, it may become part of the standard library.

---

<div class="post-metadata">

**Author:** ![SylvanM](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/sylvanm/32/30432_2.png) [@SylvanM](https://forums.swift.org/u/SylvanM)\
**Post date:** [June 18, 2023, 3:01pm UTC](https://forums.swift.org/t/bigint-status/65566/4 "2023-06-18T15:01:09Z")

</div>

Oh cool! Has Apple confirmed that or is that mostly speculation?

---

<div class="post-metadata">

**Author:** ![mgriebling](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/mgriebling/32/29936_2.png) [@mgriebling](https://forums.swift.org/u/mgriebling)\
**Post date:** [June 18, 2023, 3:02pm UTC](https://forums.swift.org/t/bigint-status/65566/5 "2023-06-18T15:02:59Z")

</div>

No confirmation from Apple about this. Unless I'm mistaken, this is one of the open-source libraries from Swift. So, not so much about what Apple wants, and more what the open source community would want.

---

<div class="post-metadata">

**Author:** ![Nevin](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/nevin/32/617_2.png) [@Nevin](https://forums.swift.org/u/Nevin)\
**Post date:** [June 18, 2023, 6:39pm UTC](https://forums.swift.org/t/bigint-status/65566/6 "2023-06-18T18:39:53Z")

</div>

> [@mgriebling](#):
>
> At least initially it will likely be released as part of the Swift Numerics library. Sometime in the future, it may become part of the standard library.

Is there an established procedure for bringing things from libraries like Numerics / Algorithms / Collections into the Standard Library?

Would, for example, `Numerics.BigInt` and `Swift.BigInt` coexist, or would Numerics remove its implementation?

If they coexist, how would we deal with APIs written for one that need to work with the other? And how would the two types be kept in sync going forward?

If the Numerics type is removed, what would happen with clients that rely on it?

---

<div class="post-metadata">

**Author:** ![mgriebling](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/mgriebling/32/29936_2.png) [@mgriebling](https://forums.swift.org/u/mgriebling)\
**Post date:** [June 19, 2023, 1:14am UTC](https://forums.swift.org/t/bigint-status/65566/7 "2023-06-19T01:14:56Z")

</div>

Don't know the answers to your questions but there will likely be just one interface definition to BigInt so no compatibility issues. Here's my version [Sources/BigIntModule/BigInt.swift](https://github.com/mgriebling/swift-numerics.git), it speeds up the string conversions in the original. Look in the BigInt branch.
