Hello JuliaLang Community! I am a social scientist making his way from the Python ecosystem (mostly numpy & pandas) to Julia, and have in general been delighted by the language – concise, generally quite readable, and performance without the need to mix in numba and Cython code all the time. But I …

Have you looked into Safer Integers ? They’re quite fast and they’ll tell you if there’s an overflow. The linked package comes with a plethora of different SafeInt types of different bit sizes.

[image] Mason: Have you looked into Safer Integers? They’re quite fast and they’ll tell you if there’s an overflow. The linked package comes with a plethora of different SafeInt types of different bit sizes. AMAZING! Thank you so much @Mason !! This is precisely the kind of solution I’ve been …

Yeah the package just came out. Its pretty neat!

Thanks for the encouragement. I just released v0.0.2, it is tighter and has some corrections. There is now the start of a background section in the README .

I think your work could be a gate to faster BigInt . I would bet that a type Union(BigInt,SafeInt) where you would switch to BigInt on overflow instead of throwing an error would be faster than the current BigInt for many computations (which need Big integers, but only infrequently).

Hello, I have a small problem with SaferIntegers, still using the same code: function collatz(lim) max=1 for i in 1:lim c=0 n=SafeUInt64(i) while n!=1 if n&1==0 n>>=1 else n=3*n+1 end c+=1 end if c>max max=c …

that is a bug – thank you for finding it … on it

@Jean_Michel this should get you through the night: function collatz(lim) max = 1 for i in 1:lim c = 0 n = SafeUInt64(i) while n != 1 if n&1==0 n = fld(n,2) # <<< this is the only edit else …

Thank you! (I found myself the workaround). I think your package is very useful. I wonder if a type Union{SafeInt , Bigint} where on overflow conversion is done could work and be faster in the above example (where most Ints are small, very few are big) than using BigInts

I did take your earlier note seriously. I am partway rewriting it and it seems to me that there could a designated SafelyWidens type. Most of the time, it is good not to widen and find the issue and then run larger if appropriate. I do understand there are important uses where one wants the widen…

A plea for int overflow checking as the default

Internals & Design

Topic		Replies	Views
Potential solution to the overflow problem; 64-bit considered harmful, 32- or 21-bit better General Usage integer-overflow	6	3830	October 18, 2021
Discussion about integer overflow Internals & Design numbers , integer-overflow	188	10049	October 15, 2021
Julia messes up integer exponents? Performance integer-overflow	106	7711	February 21, 2019
Tonight I hated julia, REPL and overflows New to Julia integer-overflow	64	6843	March 14, 2020
Wrong results in calculation Performance	21	3394	March 12, 2019

A plea for int overflow checking as the default

Related topics