BigInteger

suggest change

Remarks

When To Use

BigInteger objects are by their very nature very heavy on RAM. Consequently, they should only be used when absolutely necessary, ie for numbers on a truly astronomical scale.

Further to this, all arithmetic operations on these objects are an order of magnitude slower than their primitive counterparts, this problem gets further compounded as the number grows as they are not of a fixed size. It is therefore feasibly possible for a rogue BigInteger to cause a crash by consuming all of the available RAM.

Alternatives

If speed is imperative to your solution it may be more efficient to implement this functionality yourself using a class wrapping a Byte[] and overloading the necessary operators yourself. However, this does require a significant amount of extra effort.

Feedback about page:

Feedback:
Optional: your email if you want me to get back to you:


BigInteger:
* BigInteger

Table Of Contents
17 Regex
19 Arrays
21 Enum
22 Tuples
24 GUID
25 BigInteger
27 Looping
36 Casting
46 Methods
88 Events
92 Structs
104 Indexer
106 Stream
107 Timers
109 Threading
127 Caching
135 Pointers
147 C# Script