New upstream version 1.55.0+dfsg1

[rustc.git] / src / doc / book / src / ch03-02-data-types.md

diff --git a/src/doc/book/src/ch03-02-data-types.md b/src/doc/book/src/ch03-02-data-types.md
index 65df18b8e1e587ff6d23d8538b0137e046af241e..b97713b35ae724eef2bd40be8ae0bd184b3aff8b 100644 (file)
--- a/src/doc/book/src/ch03-02-data-types.md
+++ b/src/doc/book/src/ch03-02-data-types.md
@@ -73,8 +73,10 @@ program is running on: 64 bits if you’re on a 64-bit architecture and 32 bits
 if you’re on a 32-bit architecture.
 
 You can write integer literals in any of the forms shown in Table 3-2. Note
-that all number literals except the byte literal allow a type suffix, such as
-`57u8`, and `_` as a visual separator, such as `1_000`.
+that number literals that can be multiple numeric types allow a type suffix,
+such as `57u8`, to designate the type. Number literals can also use `_` as a
+visual separator to make the number easier to read, such as `1_000`, which will
+have the same value as if you had specified `1000`.
 
 <span class="caption">Table 3-2: Integer Literals in Rust</span>
 
@@ -87,9 +89,9 @@ that all number literals except the byte literal allow a type suffix, such as
 | Byte (`u8` only) | `b'A'`        |
 
 So how do you know which type of integer to use? If you’re unsure, Rust’s
-defaults are generally good choices, and integer types default to `i32`: this
-type is generally the fastest, even on 64-bit systems. The primary situation in
-which you’d use `isize` or `usize` is when indexing some sort of collection.
+defaults are generally good places to start: integer types default to `i32`.
+The primary situation in which you’d use `isize` or `usize` is when indexing
+some sort of collection.
 
 > ##### Integer Overflow
 >