I am attempting to use the same function forward in different contexts. Layers.jl module Layers export Dense, forward struct Dense n_inputs n_neurons weights biases function Dense(n_inputs, n_neurons) ### Intialize weights and biases ... new(n_inputs, …

[image] Kieran_Gill: What is the correct way to set up function overloading from multiple different files? The problem in your case is that you’ve now included NNFS.jl in two different places–once inside Layers.jl and again in your main file. Those separate include()s have created two complet…

The problem is that you have 2 different functions named forward instead of 1 function with 2 methods. The solution is to make one (or both) of Layers and Activations import forward before defining it.

I think that deserves a design explanation. Naively I would expect that to work and to raise a warning if a method overwrites the other. Of course for third party modules the alternative is to import. But it is somewhat scary that that kind of overwrite can happen without notice when loading multip…

Hi, thanks for your reply. I’m still having a bit of an issue doing it this way. I tried following this and reading this documentation, yet I’m still unsure as to where I’m going wrong. New file NNFS.jl module NNFS export forward forward(layer, data) = begin throw("You need to overload base …

[image] lmiq: I think that deserves a design explanation. Naively I would expect that to work and to raise a warning if a method overwrites the other. There’s no overwriting going on–there are just two different functions: Layers.forward and Activations.forward which have nothing whatsoever t…

The reason for this is that making a new function by default means you only need to be aware of the functions you extend. If a new method was created by default, any package (or Base) adding a new function would be a potentially breaking change.

My blog post may be helpful: https://www.ahsmart.com/pub/the-meaning-of-functions/ This is also the reason why you sometimes see WhateverBase.jl packages because they are used to define functions that are expected to be extended.

I am sorry, there is indeed an error raised, so that is fine: julia> module Pkg1 f(x) = 1 export f end Main.Pkg1 julia> module Pkg2 f(x) = 2 export f end Main.Pkg2 julia> using .Pkg1; using .Pkg2 julia> f(1) WARNING: both Pkg2 and Pkg1 export "f"…

Concerning the original question, here is a simplified version which might help to understand what is going on: NNFS.jl: module NNFS export forward forward(layer) = "original" end Layers.jl: module Layers include("NNFS.jl") import .NNFS.forward struct Dense x end NNFS.forward(layer::Dense) = "…

Thank you! Is there an explanation on . vs .. available somewhere? The only mention of it I can find in the documentation is here . Typically the difference between . and .. is to specify cwd or parent directory; so, I’m a bit surprised to see it being used like this.

[image] Kieran_Gill: Thank you! Is there an explanation on . vs .. available somewhere? The only mention of it I can find in the documentation is here . It’s explained at the end of this section: Modules · The Julia Language The analogy to cwd or the parent directory is intentional: the .. me…

Multiple Dispatch Across Seperate Files

General Usage

lmiq December 29, 2020, 2:59pm 14

Here is an example: Difference between "using x" vs "using .x" or "using Main.x" - #2 by lmiq

Topic		Replies	Views
What is the preferred way to use multiple files? General Usage question , modules , code-organization	15	8403	October 25, 2024
Two modules with the same exported function name but different signature General Usage question	13	6043	September 21, 2018
Multiple dispatch with module and external functions New to Julia function	4	759	January 21, 2021
Best way to implement +(x::Float32,y::Float32) in 2 different modules? General Usage	20	1904	May 4, 2018
Julia modules New to Julia	3	1038	October 28, 2018

Multiple Dispatch Across Seperate Files

Related topics