Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

import can operates on multiple names. #32676

Merged
merged 1 commit into from
Jul 26, 2019
Merged

import can operates on multiple names. #32676

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
import can operates on multiple names.
  • Loading branch information
@June-6th
June-6th committed Jul 25, 2019
commit 085f6c4dfb62b5b7b9755d0ad94f67040cd2f8d9
4 changes: 2 additions & 2 deletions doc/src/manual/modules.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,8 +46,8 @@ The statement `using BigLib: thing1, thing2` brings just the identifiers `thing1
into scope from module `BigLib`. If these names refer to functions, adding methods to them
will not be allowed (you may only "use" them, not extend them).

The [`import`](@ref) keyword supports the same syntax as [`using`](@ref), but only operates on a single name
at a time. It does not add modules to be searched the way `using` does. `import` also differs
The [`import`](@ref) keyword supports the same syntax as [`using`](@ref).
It does not add modules to be searched the way `using` does. `import` also differs
from `using` in that functions imported using `import` can be extended with new methods.

In `MyModule` above we wanted to add a method to the standard [`show`](@ref) function, so we had to write
Expand Down