From c06637ba1fd7a6cf0167c0e701f584a772c8def3 Mon Sep 17 00:00:00 2001 From: Phillip Wood Date: Mon, 26 Oct 2026 14:14:26 +0000 Subject: [PATCH] CodingGuidelines: allow compound literals Our coding guidelines say that we'll allow compound literals from mid 2026 if no problems are reported in relation to the test balloon added in 01e49941d6 (reftable/system: provide thin wrapper for tempfile subsystem, 2024-11-18). As no such reports have been received, update the guidelines to allow this construct. Signed-off-by: Phillip Wood Signed-off-by: Junio C Hamano --- Documentation/CodingGuidelines | 9 ++------- 1 file changed, 2 insertions(+), 7 deletions(-) diff --git a/Documentation/CodingGuidelines b/Documentation/CodingGuidelines index c06f5d3071..23a4d2186a 100644 --- a/Documentation/CodingGuidelines +++ b/Documentation/CodingGuidelines @@ -311,13 +311,8 @@ For C programs: . since late 2023 with 8277dbe987 we have been using the bool type from . - C99 features we have test balloons for: - - . since late 2024 with v2.48.0-rc0~20, we have test balloons for - compound literal syntax, e.g., (struct foo){ .member = value }; - our hope is that no platforms we care about have trouble using - them, and officially adopt its wider use in mid 2026. Do not add - more use of the syntax until that happens. + . since late 2024 with v2.48.0-rc0~20, we have been using compound + literals, e.g., (struct foo){ .member = value }; New C99 features that we cannot use yet: