LiarPrincess

As for any regressions: I also propose [#98 Using tests from “Violet - Python VM written in Swift”](https://github.com/attaswift/BigInt/issues/98). So, first I would add test cases and them we could (maybe)...

This is a little bit more complicated. There is no silver bullet and there are multiple ways in which you can implement a `BigInt` depending on what use-cases you target....

Anyway… I will work on adding more tests later… Btw. Take those explanations with a grain of salt. Obviously I wrote those tests (well Node generated them… but it is...

Ok. I will work on it next week. Obviously it will be multiple smaller PRs rather than a single big one. All of them will be linked to this issue....

Additional reference: [loftwareArrayOfOptional](https://github.com/loftware/ArrayOfOptional/blob/332f3ed0e6dfcefabbedc8e6df66f465403c2ed8/ArrayOfOptional.swift#L52) (Dave Abrahams thingy).

Anyway, we will probably end up with garbage collector without any of the `retain`/`release`/`ref count`. As for the exact choices: - **serial** vs **parallel** - in serial collection, only one...

After some thoughts, there is a way to implement a nice garbage collection in Swift. The catch is that it requires move-only types. ## Semantics - assign (`=`) is `move`...

I added the test for rounding toward 0: `|quotient * rhs|

[3.2.2023] EDIT to main issue: - [[BigInt tests] 💀 Init from float 754](https://github.com/apple/swift-numerics/pull/258) - [[BigInt tests] ✅🐰 Codable](https://github.com/apple/swift-numerics/pull/259) - many changes in performance tests

Things to do in `Helpers` (but I'm not going to update 15 PRs, so we will do it later): - add `reserveCapacity` in `generate[Big]Ints` - this does not matter in...