Hello, I have the following situation which I did not expected: defining a fucntion with the same name but different signature in two modules like this: ## Module RawTables function save(T::RawTable, name_pref::String) ... end ## Module RawPlots function save(T::RawPlot, name_pref::String) ... end…

Just because two generic function (which is the container of the methods) have the same name, does not mean that they are the same object (you can check this with ===). You need to extend the generic function defined in one module in the other; just like with Base functions: julia> module A …

Thanks. But this implies that the modules have to know about each other, which is not useful for anything else. And I have to specify the hierarchy which module extends the other one? Maybe there can be some check whether the name exists and extend it or otherwise create a new object? I mean, e. g…

No; just that you have to know about another module if you want to extend methods of that specific module when developing a module. Otherwise you just have to specify which modules version you intended to use when actually using both modules at the same time.

Thank you for the link. Well, I have looked through it and I clearly would vote for a possibility to have common function names from different modules to work together smoothly without the need to import them or state the module explicitly :wink: But this is only my option…

[image] stakaz: without the need to import them They already do; if you only import one of them, that warning is not going to show up. It shows up in the example provided by @mauro3 because they’re both contained in the top level scope Main and are referencing each other and are thus loaded b…

This is exactly the problem I have. Neither do I extend the save behavior nor do I want to specify the module name because I call the save function with a type which clearly can decide the right version of the function for me. In my option this is a very clear case of “do the same thing” bit still …

I can understand that this can lead to errors on the big scale but for some very common words which are not in Base I really would like to see a way to do this. For convenience, not because it is logically the best option for a programming language and all this discussion about “doing the same thing…

You should hook into https://github.com/JuliaIO/FileIO.jl for load/save.

You made my day. A logical and obvious solution which I did not considered. Thanks

Two modules with the same exported function name but different signature

General Usage

mauro3 September 20, 2018, 1:07pm 4

This has been discussed at length, the latest was Function name conflict: ADL / function merging?.

Topic		Replies	Views
Same function name in multiple modules? General Usage	5	1096	October 28, 2018
What is the best way to override a function in different modules? New to Julia	4	2684	January 28, 2021
Function conflict with different signatures General Usage question , modules , code-organization	5	518	October 21, 2022
Functions from different modules with the same name General Usage pluto , namespaces	16	5721	May 20, 2021
Warning about name conflict General Usage	6	359	February 21, 2024

Two modules with the same exported function name but different signature

Related topics