Skip to main content
Code Review

Return to Answer

replaced http://stackoverflow.com/ with https://stackoverflow.com/
Source Link

Int faster than Integer. If you have acceptable limitations you should use Int.

"Integer" is an arbitrary precision type: it will hold any number no matter how big, up to the limit of your machine's memory.... This means you never have arithmetic overflows. On the other hand it also means your arithmetic is relatively slow. Lisp users may recognise the "bignum" type here.

"Int" is the more common 32 or 64 bit integer. Implementations vary, although it is guaranteed to be at least 30 bits.

Source: The Haskell Wikibook. Also, you may find the Numbers section of A Gentle Introduction to Haskell useful.

Copy-paste from Haskell Int and Integer Haskell Int and Integer

Int faster than Integer. If you have acceptable limitations you should use Int.

"Integer" is an arbitrary precision type: it will hold any number no matter how big, up to the limit of your machine's memory.... This means you never have arithmetic overflows. On the other hand it also means your arithmetic is relatively slow. Lisp users may recognise the "bignum" type here.

"Int" is the more common 32 or 64 bit integer. Implementations vary, although it is guaranteed to be at least 30 bits.

Source: The Haskell Wikibook. Also, you may find the Numbers section of A Gentle Introduction to Haskell useful.

Copy-paste from Haskell Int and Integer

Int faster than Integer. If you have acceptable limitations you should use Int.

"Integer" is an arbitrary precision type: it will hold any number no matter how big, up to the limit of your machine's memory.... This means you never have arithmetic overflows. On the other hand it also means your arithmetic is relatively slow. Lisp users may recognise the "bignum" type here.

"Int" is the more common 32 or 64 bit integer. Implementations vary, although it is guaranteed to be at least 30 bits.

Source: The Haskell Wikibook. Also, you may find the Numbers section of A Gentle Introduction to Haskell useful.

Copy-paste from Haskell Int and Integer

added 829 characters in body
Source Link
outoftime
  • 1.8k
  • 10
  • 18

Int faster than Integer. If you have acceptable limitations you should use Int.

"Integer" is an arbitrary precision type: it will hold any number no matter how big, up to the limit of your machine's memory.... This means you never have arithmetic overflows. On the other hand it also means your arithmetic is relatively slow. Lisp users may recognise the "bignum" type here.

"Int" is the more common 32 or 64 bit integer. Implementations vary, although it is guaranteed to be at least 30 bits.

Source: The Haskell Wikibook . Also, you may find the Numbers section of A Gentle Introduction to Haskell useful.

Copy-paste from Haskell Int and Integer

Int faster than Integer. If you have acceptable limitations you should use Int.

Int faster than Integer. If you have acceptable limitations you should use Int.

"Integer" is an arbitrary precision type: it will hold any number no matter how big, up to the limit of your machine's memory.... This means you never have arithmetic overflows. On the other hand it also means your arithmetic is relatively slow. Lisp users may recognise the "bignum" type here.

"Int" is the more common 32 or 64 bit integer. Implementations vary, although it is guaranteed to be at least 30 bits.

Source: The Haskell Wikibook . Also, you may find the Numbers section of A Gentle Introduction to Haskell useful.

Copy-paste from Haskell Int and Integer

deleted 1 character in body
Source Link
Ethan Bierlein
  • 15.9k
  • 4
  • 60
  • 146

Int faster than IntergerInteger. If you have acceptable limitations you should use Int.

Int faster than Interger. If you have acceptable limitations you should use Int.

Int faster than Integer. If you have acceptable limitations you should use Int.

Source Link
outoftime
  • 1.8k
  • 10
  • 18
Loading
lang-hs

AltStyle によって変換されたページ (->オリジナル) /