make using A.B only for modules, using A: B only for single bindings
#25306
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
JeffBezanson
added
modules
triage
|
Triage hearts. |
JeffBezanson
force-pushed
the
jb/simpler_using
branch
from
d600223
to
b82b5c8
Compare
tpapp
added a commit
to tpapp/julia
that referenced
this pull request
Nov 2, 2020
Main changes Namespaces, export, import, using - explain namespaces, qualified symbol names, and export lists - consolidate examples where applicable - fix examples which were outdated after JuliaLang#25306 - distribute the “Namespace miscellanea” section into parts in the appropriate sections - break up the summary table and explain each case in detail with examples - subsection on various strategies to handle symbol conflicts - use “bring into the namespace/scope” instead of “import” in the text, as readers confuse it with `import` - explicitly document what happens with multiple `using` / `import` statements - add relevant style / best practices suggestions which are now widely used in the Julia ecosystem Submodules - discuss usage of `using ParentModule.SubModule` etc (relies on code loading) - add submodule examples where order matters, fixes JuliaLang#38011 (also another example by @rdeits [from Discourse](https://discourse.julialang.org/t/problem-with-using-in-submodules/42321/2)) - mention that submodules do not “inherit” scope from parent Misc incidental changes - in the Methods chapter, add a note about adding methods to functions in other modules - add a markdown id to the code-loading chapter The “Module initialization and precompilation” section is left unchanged.
timholy
added a commit
that referenced
this pull request
Nov 5, 2020
* Reorganize the Modules chapter of the manual. Main changes Namespaces, export, import, using - explain namespaces, qualified symbol names, and export lists - consolidate examples where applicable - fix examples which were outdated after #25306 - distribute the “Namespace miscellanea” section into parts in the appropriate sections - break up the summary table and explain each case in detail with examples - subsection on various strategies to handle symbol conflicts - use “bring into the namespace/scope” instead of “import” in the text, as readers confuse it with `import` - explicitly document what happens with multiple `using` / `import` statements - add relevant style / best practices suggestions which are now widely used in the Julia ecosystem Submodules - discuss usage of `using ParentModule.SubModule` etc (relies on code loading) - add submodule examples where order matters, fixes #38011 (also another example by @rdeits [from Discourse](https://discourse.julialang.org/t/problem-with-using-in-submodules/42321/2)) - mention that submodules do not “inherit” scope from parent Misc incidental changes - in the Methods chapter, add a note about adding methods to functions in other modules - add a markdown id to the code-loading chapter The “Module initialization and precompilation” section is left unchanged. Co-authored-by: Tim Holy <[email protected]> Co-authored-by: Simon Byrne <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
part of #8000