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

Replace incorrect term "parent modules" with "ancestor modules". #806

Merged
merged 2 commits into from
May 2, 2020
Merged

Replace incorrect term "parent modules" with "ancestor modules". #806

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
84761dc
Replace incorrect term "parent modules" with "ancestor modules".
TeemuRemes May 1, 2020
f41afd4
Update another usage of "parent" to "ancestor"
ehuss May 2, 2020
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
4 changes: 2 additions & 2 deletions src/visibility-and-privacy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ With the notion of an item being either public or private, Rust allows item
accesses in two cases:

1. If an item is public, then it can be accessed externally from some module
`m` if you can access all the item's parent modules from `m`. You can
`m` if you can access all the item's ancestor modules from `m`. You can
also potentially be able to name the item through re-exports. See below.
2. If an item is private, it may be accessed by the current module and its
descendants.
Expand Down Expand Up @@ -148,7 +148,7 @@ In addition to public and private, Rust allows users to declare an item as
visible only within a given scope. The rules for `pub` restrictions are as
follows:
- `pub(in path)` makes an item visible within the provided `path`. `path` must
be a parent module of the item whose visibility is being declared.
be an ancestor module of the item whose visibility is being declared.
- `pub(crate)` makes an item visible within the current crate.
- `pub(super)` makes an item visible to the parent module. This is equivalent
to `pub(in super)`.
Expand Down