New upstream version 1.24.1+dfsg1

[rustc.git] / src / doc / nomicon / src / repr-rust.md

diff --git a/src/doc/nomicon/src/repr-rust.md b/src/doc/nomicon/src/repr-rust.md
index 7001d3221eb5ce7f41470a0b45e4c9bfa0f499ba..c975090220b5e6151bff3a23b82f5a2f544d316c 100644 (file)
--- a/src/doc/nomicon/src/repr-rust.md
+++ b/src/doc/nomicon/src/repr-rust.md
@@ -21,7 +21,7 @@ Rust gives you the following ways to lay out composite data:
 * arrays (homogeneous product types)
 * enums (named sum types -- tagged unions)
 
-An enum is said to be *C-like* if none of its variants have associated data.
+An enum is said to be *field-less* if none of its variants have associated data.
 
 Composite structures will have an alignment equal to the maximum
 of their fields' alignment. Rust will consequently insert padding where
@@ -110,9 +110,6 @@ struct Foo<u32, u16> {
 The latter case quite simply wastes space. An optimal use of space therefore
 requires different monomorphizations to have *different field orderings*.
 
-**Note: this is a hypothetical optimization that is not yet implemented in Rust
-1.0**
-
 Enums make this consideration even more complicated. Naively, an enum such as:
 
 ```rust