a tuple of values is spliced into a varargs call precisely where the variable number of arguments go. This need not be the case, however: julia> x = (2, 3, 4) (2, 3, 4) julia> bar(1,x...) (1, 2, (3 function body into the REPL to debug it—you have to add global annotations and then remove them again to go back; 2. Beginners will write this kind of code without the global and have no idea why their code myfilter(Apadded, kernel, NoPad()) # indicate the new boundary conditions end # other padding methods go here function myfilter(A, kernel, ::NoPad) # Here's the "real" implementation of the core computation

a tuple of values is spliced into a varargs call precisely where the variable number of arguments go. This need not be the case, however: julia> x = (2, 3, 4) (2, 3, 4) julia> bar(1,x...) (1, 2, (3 function body into the REPL to debug it—you have to add global annotations and then remove them again to go back; 2. Beginners will write this kind of code without the global and have no idea why their code myfilter(Apadded, kernel, NoPad()) # indicate the new boundary conditions end # other padding methods go here function myfilter(A, kernel, ::NoPad) # Here's the "real" implementation of the core computation

a tuple of values is spliced into a varargs call precisely where the variable number of arguments go. This need not be the case, however: julia> x = (2, 3, 4) (2, 3, 4) julia> bar(1,x...) (1, 2, (3 function body into the REPL to debug it—you have to add global annotations and then remove them again to go back; 2. Beginners will write this kind of code without the global and have no idea why their code myfilter(Apadded, kernel, NoPad()) # indicate the new boundary conditions end # other padding methods go here function myfilter(A, kernel, ::NoPad) # Here's the "real" implementation of the core computation

a tuple of values is spliced into a varargs call precisely where the variable number of arguments go. This need not be the case, however:CHAPTER 9. FUNCTIONS 85 julia> x = (2, 3, 4) (2, 3, 4) julia> function body into the REPL to debug it—you have to add global annotations and then remove them again to go back; 2. Beginners will write this kind of code without the global and have no idea why their code myfilter(Apadded, kernel, NoPad()) # indicate the new boundary conditions end # other padding methods go here function myfilter(A, kernel, ::NoPad) # Here's the "real" implementation of the core computation

a tuple of values is spliced into a varargs call precisely where the variable number of arguments go. This need not be the case, however:CHAPTER 9. FUNCTIONS 85 julia> x = (2, 3, 4) (2, 3, 4) julia> function body into the REPL to debug it—you have to add global annotations and then remove them again to go back; 2. Beginners will write this kind of code without the global and have no idea why their code myfilter(Apadded, kernel, NoPad()) # indicate the new boundary conditions end # other padding methods go here function myfilter(A, kernel, ::NoPad) # Here's the "real" implementation of the core computation

a tuple of values is spliced into a varargs call precisely where the variable number of arguments go. This need not be the case, however: julia> x = (2, 3, 4) (2, 3, 4) julia> bar(1,x...) (1, 2, (3 function body into the REPL to debug it—you have to add global annotations and then remove them again to go back; 2. Beginners will write this kind of code without the global and have no idea why their code myfilter(Apadded, kernel, NoPad()) # indicate the new boundary conditions end # other padding methods go here function myfilter(A, kernel, ::NoPad) # Here's the "real" implementation of the core computation

a tuple of values is spliced into a varargs call precisely where the variable number of arguments go. This need not be the case, however: julia> x = (2, 3, 4) (2, 3, 4) julia> bar(1,x...) (1, 2, (3 function body into the REPL to debug it—you have to add global annotations and then remove them again to go back; 2. Beginners will write this kind of code without the global and have no idea why their code myfilter(Apadded, kernel, NoPad()) # indicate the new boundary conditions end # other padding methods go here function myfilter(A, kernel, ::NoPad) # Here's the "real" implementation of the core computation

a tuple of values is spliced into a varargs call precisely where the variable number of arguments go. This need not be the case, however: julia> x = (2, 3, 4) (2, 3, 4) julia> bar(1,x...) (1, 2, (3 function body into the REPL to debug it—you have to add global annotations and then remove them again to go back; 2. Beginners will write this kind of code without the global and have no idea why their code myfilter(Apadded, kernel, NoPad()) # indicate the new boundary conditions end # other padding methods go here function myfilter(A, kernel, ::NoPad) # Here's the "real" implementation of the core computation

a tuple of values is spliced into a varargs call precisely where the variable number of arguments go. This need not be the case, however: julia> x = (2, 3, 4) (2, 3, 4) julia> bar(1,x...) (1, 2, (3 function body into the REPL to debug it—you have to add global annotations and then remove them again to go back; 2. Beginners will write this kind of code without the global and have no idea why their code myfilter(Apadded, kernel, NoPad()) # indicate the new boundary conditions end # other padding methods go here function myfilter(A, kernel, ::NoPad) # Here�s the "real" implementation of the core computation

a tuple of values is spliced into a varargs call precisely where the variable number of arguments go. This need not be the case, however: julia> x = (2, 3, 4) (2, 3, 4) julia> bar(1,x...) (1, 2, (3 function body into the REPL to debug it—you have to add global annotations and then remove them again to go back; 2. Beginners will write this kind of code without the global and have no idea why their code myfilter(Apadded, kernel, NoPad()) # indicate the new boundary conditions end # other padding methods go here function myfilter(A, kernel, ::NoPad) # Here's the "real" implementation of the core computation