Industrial standards for Julia packages

[chakravala]

This issue has been discussed in multiple threads already, most famously

Function name conflict: ADL / function merging?

Is there any reason why Julia needs me to fully qualify the function name when the argument types are clear and there shouldn’t be any problem with multiple dispatch? Case 1: load JuliaDB before defining Foo julia> using JuliaDB julia> stack( stack(t::D) where D<:Union{IndexedTables.NDSparse, IndexedTables.NextTable} in IndexedTables at /Users/tomkwong/.julia/v0.6/IndexedTables/src/reshape.jl:32 stack(t::D, by; select, variable, value) where D<:Union{IndexedTables.NDSparse, IndexedTables.Next…

There are a few issues with the whole function merging thing, one of my solution is the ForceImport package

GitHub - chakravala/ForceImport.jl: Macro that force imports conflicting...

which helps with selective managing of the local merging of namespaces (at least for Base methods). Now, I’m thinking I could extend this package to work with a specified package, not only Base methods.

Here is an explanation of how it is used

Operations on expressions

The principle which all @force users must keep in mind is this: the goal is to extend Base methods locally without affecting the global method table by type piracy, and to be able to import them into another package to have the same local effect. In order to avoid the type piracy, one must define a new local complementary n-ary method that will fall back on the base method with Any arguments. Then there will be a tiered alternative dispatch layer within the local package scope that redirects to …