Skip to content

Commit aa0ce07

Browse files
authored
Unify some of the language from #53428
1 parent eb9c668 commit aa0ce07

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

base/docs/basedocs.jl

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -39,13 +39,13 @@ the name `foo`), whether they are `export`ed or not.
3939
See the [manual section about modules](@ref modules) for details.
4040
4141
!!! note
42-
Doing `using Foo` in packages or code that you want to keep working with
43-
updated dependencies is not recommended. The reason for this is if another
44-
dependency starts to export one of the same names as `Foo` the code will
45-
error due to an ambiguity in which package the name should be taken from.
46-
Instead, explicitly list what names you want to use from Foo, for example:
47-
`using Foo: Foo, parsefile, readfile` to get access bring `Foo` and two
48-
functions `parsefile` and `readfile` into scope.
42+
Qualifying the names being used as in `using Foo: Foo, f` is
43+
recommended over plain `using Foo` for released packages and other
44+
code which is meant to be re-used in the future with updated dependencies
45+
or future versions of julia. When two modules or packages export the same name
46+
and both are loaded with `using` (without the explicit list), it is an error to use
47+
that name without qualification. Using an explicit list ensures that new exports
48+
in updated dependencies do not break the forward compatibility of the code.
4949
"""
5050
kw"using"
5151

0 commit comments

Comments
 (0)