From 096fa1c0c0a466afd61e3d603ab03b5a41322d07 Mon Sep 17 00:00:00 2001 From: Esteban Kuber Date: Tue, 29 Oct 2024 10:18:16 -0700 Subject: [PATCH] Update text/0000-default-field-values.md Co-authored-by: Felix S Klock II --- text/0000-default-field-values.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/text/0000-default-field-values.md b/text/0000-default-field-values.md index b99b693705d..5203cfd205b 100644 --- a/text/0000-default-field-values.md +++ b/text/0000-default-field-values.md @@ -1047,8 +1047,8 @@ There are many reasons for this restriction: As an alternative to the proposed design is either explicitly writing out `..Default::default()` or extending the language such that `Foo { .. }` becomes -sugar for `Foo { ..Default::default() }`. While the latter idea does not satisfy -any of the [motivation] set out, the former does to a small extent. +sugar for `Foo { ..Default::default() }`. While the former idea does not satisfy +any of the [motivation] set out, the latter does to a small extent. In particular, `Foo { .. }` as sugar slightly improves ergonomics. However, it has some notable problems: