Update modules.rst

[dletozeun]

Hello,

reading the Julia modules documentation I found the summary table a bit misleading IMHO.

So I updated the summary table in a way that is showing that in any case, it is possible to overload the module functions when whole module or any of its function is brought into the current scope using "using" or "import" statements. Instead what changes is the cases "exports" are brought into scope or not and when it is possible to overload it or not.

I am not a Julia expert so please let me know if I am mistaken.

[nolta]

I see your point, but i worry this patch makes the table harder to read because every cell would contain MyModule.x, MyModule.y, MyModule.p.

[dletozeun]

Yes I agree, I had the same thought actually and I was thinking that maybe we could remove these "MyModule.x, MyModule.y, MyModule.p" and add a short notice after the table like:

Note: In all cases, MyModule.x, MyModule.y and MyModule.p are loaded into current workspace and it is possible to add methods to them.

[ivarne]

Maybe we could write MyModule.* or something (with a note explaining that in this context * is all variables in MyModule, not just the multiplication operator)

[rfourquet]

While the attention is on this table: it took me time to even notice that there is a third colum in this table (in the online docs): if I notice the scroll bar at all, it seems to me that it would only help to see one last variable in the first row and I won't bother to scroll. It's very boring to have to scroll when the webpage could already show everything. Could readthedocs be adjusted?

[dletozeun]

There is an update of the documentation inspired from what was suggested in the above discussion.

[JeffBezanson]

This is incorrect. import MyModule.x only makes x visible, not MyModule.

[JeffBezanson]

Please revert.

[jiahao]

Ugh, sorry. Clicked the wrong button.

[dletozeun]

@JeffBezanson please correct me if I am wrong but here is what I did:

I created a file MyModule.jl then opened a julia console and typed: import MyModule.x.
After that, as expected x is brought into scope but also MyModule.x, MyModule.y and MyModule.p (See screenshot)

[StefanKarpinski]

@dletozeun, this is an (unfortunate) artifact of the fact that at the REPL, you are in the Main module, which is also the root module – where top-level module bindings are created. If you do the same thing in a module other than Main, you will not see a binding for MyModule in that module.

[dletozeun]

@StefanKarpinski Oh I see, thank you for the clarification!