MethodError: objects of type Int64 are not callable Both expressions are interpreted as function application: any expression that is not a numeric literal, when immediately followed by a parenthetical, is like Int (see Overflow behavior). If we had declared our function as fib(n::Int), however, the application to BigInt would have been prevented for no reason. In general, you should use the most general julia> +(1,2,3) 6 CHAPTER 8. FUNCTIONS 71 The infix form is exactly equivalent to the function application form – in fact the former is parsed to produce the function call internally. This also means that

MethodError: objects of type Int64 are not callable Both expressions are interpreted as function application: any expression that is not a numeric literal, when immediately followed by a parenthetical, is like Int (see Overflow behavior). If we had declared our function as fib(n::Int), however, the application to BigInt would have been prevented for no reason. In general, you should use the most general julia> 1 + 2 + 3 6 julia> +(1,2,3) 6 The infix form is exactly equivalent to the function application form – in fact the former is parsed to produce the function call internally. This also means that

MethodError: objects of type Int64 are not callable Both expressions are interpreted as function application: any expression that is not a numeric literal, when immediately followed by a parenthetical, is like Int (see Overflow behavior). If we had declared our function as fib(n::Int), however, the application to BigInt would have been prevented for no reason. In general, you should use the most general julia> 1 + 2 + 3 6 julia> +(1,2,3) 6 The infix form is exactly equivalent to the function application form – in fact the former is parsed to produce the function call internally. This also means that

MethodError: objects of type Int64 are not callable Both expressions are interpreted as function application: any expression that is not a numeric literal, when immediately followed by a parenthetical, is like Int (see Overflow behavior). If we had declared our function as fib(n::Int), however, the application to BigInt would have been prevented for no reason. In general, you should use the most general julia> 1 + 2 + 3 6 julia> +(1,2,3) 6 The infix form is exactly equivalent to the function application form – in fact the former is parsed to produce the function call internally. This also means that

MethodError: objects of type Int64 are not callable Both expressions are interpreted as function application: any expression that is not a numeric literal, when immediately followed by a parenthetical, is like Int (see Overflow behavior). If we had declared our function as fib(n::Int), however, the application to BigInt would have been prevented for no reason. In general, you should use the most general julia> +(1,2,3) 6 CHAPTER 8. FUNCTIONS 71 The infix form is exactly equivalent to the function application form – in fact the former is parsed to produce the function call internally. This also means that

MethodError: objects of type Int64 are not callable Both expressions are interpreted as function application: any expression that is not a numeric literal, when immediately followed by a parenthetical, is like Int (see Overflow behavior). If we had declared our function as fib(n::Int), however, the application to BigInt would have been prevented for no reason. In general, you should use the most general julia> +(1,2,3) 6 CHAPTER 8. FUNCTIONS 71 The infix form is exactly equivalent to the function application form – in fact the former is parsed to produce the function call internally. This also means that

MethodError: objects of type Int64 are not callable Both expressions are interpreted as function application: any expression that is not a numeric literal, when immediately followed by a parenthetical, is like Int (see Overflow behavior). If we had declared our function as fib(n::Int), however, the application to BigInt would have been prevented for no reason. In general, you should use the most general julia> 1 + 2 + 3 6 julia> +(1,2,3) 6 The infix form is exactly equivalent to the function application form – in fact the former is parsed to produce the function call internally. This also means that

MethodError: objects of type Int64 are not callable Both expressions are interpreted as function application: any expression that is not a numeric literal, when immediately followed by a parenthetical, is like Int (see Overflow behavior). If we had declared our function as fib(n::Int), however, the application to BigInt would have been prevented for no reason. In general, you should use the most general julia> 1 + 2 + 3 6 julia> +(1,2,3) 6 The infix form is exactly equivalent to the function application form – in fact the former is parsed to produce the function call internally. This also means that

MethodError: objects of type Int64 are not callable Both expressions are interpreted as function application: any expression that is not a numeric literal, when immediately followed by a parenthetical, is like Int (see Overflow behavior). If we had declared our function as fib(n::Int), however, the application to BigInt would have been prevented for no reason. In general, you should use the most general julia> 1 + 2 + 3 6 julia> +(1,2,3) 6 The infix form is exactly equivalent to the function application form – in fact the former is parsed to produce the function call internally. This also means that

MethodError: objects of type Int64 are not callable Both expressions are interpreted as function application: any expression that is not a numeric literal, when immediately followed by a parenthetical, is like Int (see Overflow behavior). If we had declared our function as fib(n::Int), however, the application to BigInt would have been prevented for no reason. In general, you should use the most general julia> 1 + 2 + 3 6 julia> +(1,2,3) 6 The infix form is exactly equivalent to the function application form – in fact the former is parsed to produce the function call internally. This also means that