Skip to content

[manual] Mention import Foo as _ #58665

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

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
+15 −1
Open

[manual] Mention import Foo as _ #58665

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
e8b976f
Mention `import Foo as _`
ericphanson Jun 7, 2025
a49035e
Update doc/src/manual/modules.md
ericphanson Jun 7, 2025
aaa99ae
Merge branch 'master' into patch-2
ericphanson Jul 15, 2025
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
16 changes: 15 additions & 1 deletion doc/src/manual/modules.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -260,7 +260,21 @@ import BenchmarkTools as BT

`as` works with `using` only when a single identifier is brought into scope.
For example `using CSV: read as rd` works, but `using CSV as C` does not, since it operates
on all of the exported names in `CSV`.
on all of the exported names in `CSV`. Packages can also be renamed to `_`, for example

```julia
import ForwardDiff as _
```

Or, with `using`:

```julia
using ForwardDiff: ForwardDiff as _
```

This has the effect of loading the package while bringing none of its names (even the module name)
in your namespace. This is useful to communicate that a package is only loaded for the methods it
provides, instead of its names.

### Mixing multiple `using` and `import` statements

Expand Down