A plea for int overflow checking as the default

# Option 1: Using the Checked keyword
function add(a::Int, b::Int)
    return Checked(a + b)
end

# Option 2: Using the @checked macro
function add(a::Int, b::Int)
    return @checked(a + b)
end

# Option 3: Using the OverflowError exception
function add(a::Int, b::Int)
    try
        return a + b
    catch e
        if isa(e, OverflowError)
            error("Integer overflow occurred")
        else
            rethrow(e)
        end
    end
end

Option 1: Using the Checked keyword

One way to solve the problem of integer overflow in Julia is by using the Checked keyword. This keyword ensures that any arithmetic operation on integers will check for overflow and throw an exception if it occurs. In the provided code, the add function takes two integer arguments and returns their sum using the Checked keyword. If an overflow occurs, an exception will be thrown.

Option 2: Using the @checked macro

Another way to handle integer overflow in Julia is by using the @checked macro. This macro automatically inserts the Checked keyword before any arithmetic operation on integers, ensuring that overflow is checked. In the given code, the add function is defined with the @checked macro, which guarantees that the sum of the two integers will be checked for overflow.

Option 3: Using the OverflowError exception

A third approach to address integer overflow in Julia is by using the OverflowError exception. In this method, the add function attempts to perform the arithmetic operation without any explicit checks. However, if an overflow occurs, the code catches the OverflowError exception and handles it accordingly. In the provided code, the add function is wrapped in a try-catch block, and if an OverflowError is caught, an error message is displayed.

Among the three options, the best choice depends on the specific requirements of the application. Option 1 and Option 2 provide a more proactive approach by explicitly checking for overflow during arithmetic operations. This can help catch potential issues early on and prevent unexpected behavior. Option 3, on the other hand, allows for more flexibility in handling overflow errors, as it provides an opportunity to customize the error message or take alternative actions. Ultimately, the choice should be based on the desired behavior and error handling strategy of the application.