Using "Module.jl" as alias to include("Module.jl"); using .Module

[lungben]

There is already an issue with a suggestion like this, see

relative using/import should search current directory

and

[ANN] PatModules.jl: a better module system for Julia

The issue is not double inclusion, but the inclusion order. This can cause a lot mental burden and should be handled by the compiler since the compiler knows which module depends on which, e.g when you have include("B.jl") include("A.jl") where module B depends on A, manual include will result in undefined error, but if we implement issue 4600, then we can just write something like (the syntax is not decided yet) using .B from "B.jl" using .A from "A.jl" or using .A from "A.jl" using .B fr…