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

Fixed clunky grammar, that was difficult to read. #3763

Closed
wants to merge 2 commits into from
Closed

Fixed clunky grammar, that was difficult to read. #3763

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f1c531c
Fixed clunky grammar, that was difficult to read.
Rossnkama Oct 29, 2023
1de9e3e
Removed unnecessary changes, leaving only core change
Rossnkama Oct 31, 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
2 changes: 1 addition & 1 deletion src/ch08-02-strings.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -320,7 +320,7 @@ index to determine how many valid characters there were.
Indexing into a string is often a bad idea because it’s not clear what the
return type of the string-indexing operation should be: a byte value, a
character, a grapheme cluster, or a string slice. If you really need to use
indices to create string slices, therefore, Rust asks you to be more specific.
indices to create string slices, Rust asks you to be more specific.

Rather than indexing using `[]` with a single number, you can use `[]` with a
range to create a string slice containing particular bytes:
Expand Down