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

Fix typo in Chapter 7 Section 3 #3743

Merged
merged 2 commits into from
Mar 27, 2024
Merged

Fix typo in Chapter 7 Section 3 #3743

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
08d3496
Fix typo in Chapter 7 Section 3
matthewjnield Oct 8, 2023
1402554
Fix typo in Chapter 7 Section 3
matthewjnield Oct 8, 2023
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/ch07-03-paths-for-referring-to-an-item-in-the-module-tree.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -184,8 +184,8 @@ interested in this topic, see [The Rust API Guidelines][api-guidelines].
> well as a *src/lib.rs* library crate root, and both crates will have the
> package name by default. Typically, packages with this pattern of containing
> both a library and a binary crate will have just enough code in the binary
> crate to start an executable that calls code with the library crate. This
> lets other projects benefit from the most functionality that the package
> crate to start an executable that calls code within the library crate. This
> lets other projects benefit from most of the functionality that the package
> provides, because the library crate’s code can be shared.
>
> The module tree should be defined in *src/lib.rs*. Then, any public items can
Expand Down