subject:"\[Issue 17746\] Improve BigInt memory usage"

[Issue 17746] Improve BigInt memory usage

2022-12-17 Thread d-bugmail--- via Digitalmars-d-bugs

https://issues.dlang.org/show_bug.cgi?id=17746 Iain Buclaw changed: What|Removed |Added Priority|P1 |P4 --

[Issue 17746] Improve BigInt memory usage

2018-01-02 Thread d-bugmail--- via Digitalmars-d-bugs

https://issues.dlang.org/show_bug.cgi?id=17746 --- Comment #3 from Jack Stouffer --- On the other hand, if the COW is to avoid issues in code like this ``` BigInt a = 10; BigInt b = a; ++a; assert(b == 10); ``` where b could end up equaling 11, can we just make opAssign and the this(T : BigInt

[Issue 17746] Improve BigInt memory usage

2018-01-02 Thread d-bugmail--- via Digitalmars-d-bugs

https://issues.dlang.org/show_bug.cgi?id=17746 --- Comment #2 from hst...@quickfur.ath.cx --- If the BigInt is const, then the best we can do is to create a new BigInt to hold the result of the operation, i.e., what BigInt does now. For the optimization to have significant benefits, we pretty muc

[Issue 17746] Improve BigInt memory usage

2018-01-02 Thread d-bugmail--- via Digitalmars-d-bugs

https://issues.dlang.org/show_bug.cgi?id=17746 --- Comment #1 from Jack Stouffer --- >From my initial investigation into this, adding ref counting to BigInt is much more complicated than it first appears. Adding a size_t ref count on the heap for BigUint basically breaks the rest of BigInt becaus