From 4e755a96a74b7d79a8796f78a194efca5d6d649b Mon Sep 17 00:00:00 2001 From: Yuki Okushi Date: Mon, 14 Jun 2021 07:05:14 +0900 Subject: [PATCH] Adjust documentation --- compiler/rustc_error_codes/src/error_codes/E0690.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/compiler/rustc_error_codes/src/error_codes/E0690.md b/compiler/rustc_error_codes/src/error_codes/E0690.md index 1673456580a..ba706ad2b02 100644 --- a/compiler/rustc_error_codes/src/error_codes/E0690.md +++ b/compiler/rustc_error_codes/src/error_codes/E0690.md @@ -1,19 +1,19 @@ -A struct with the representation hint `repr(transparent)` had zero or more than -one fields that were not guaranteed to be zero-sized. +A struct with the representation hint `repr(transparent)` had two or more fields +that were not guaranteed to be zero-sized. Erroneous code example: ```compile_fail,E0690 #[repr(transparent)] -struct LengthWithUnit { // error: transparent struct needs exactly one +struct LengthWithUnit { // error: transparent struct needs at most one value: f32, // non-zero-sized field, but has 2 unit: U, } ``` Because transparent structs are represented exactly like one of their fields at -run time, said field must be uniquely determined. If there is no field, or if -there are multiple fields, it is not clear how the struct should be represented. +run time, said field must be uniquely determined. If there are multiple fields, +it is not clear how the struct should be represented. Note that fields of zero-sized types (e.g., `PhantomData`) can also exist alongside the field that contains the actual data, they do not count for this error. When generic types are involved (as in the above example), an error is -- 2.44.0