Skip to content

Fix confusing wording about cargo update #4818

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
sijow wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Fix confusing wording about cargo update #4818

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
2 changes: 1 addition & 1 deletion src/ch02-00-guessing-game-tutorial.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -473,7 +473,7 @@ checked into source control with the rest of the code in your project.
When you _do_ want to update a crate, Cargo provides the command `update`,
which will ignore the _Cargo.lock_ file and figure out all the latest versions
that fit your specifications in _Cargo.toml_. Cargo will then write those
versions to the _Cargo.lock_ file. Otherwise, by default, Cargo will only look
versions to the _Cargo.lock_ file. Given our specification `0.10.1`, Cargo will only look
for versions greater than 0.10.1 and less than 0.11.0. If the `rand` crate has
released the two new versions 0.10.2 and 0.999.0, you would see the following if
you ran `cargo update`:
Expand Down