[PATCH v2 5/5] Documentation: consistently use spaces inside initializers
- From
Patrick Steinhardt <ps@pks.im>
- Date
- Jul 30, 2024, 07:24 UTC
- Message-ID
- <8789323ac770e00707df4708994f7767bf57b00f.1722323818.git.ps@pks.im>
- In-Reply-To
- <cover.1722323818.git.ps@pks.im>
Our coding guide is inconsistent with how it uses spaces inside of initializers (`struct foo bar = { something }`). While we mostly carry the space between open and closing braces and the initialized members, in one case we don't.
Fix this one instance such that we consistently carry the space. This is also consistent with how clang-format formats such initializers.
Signed-off-by: Patrick Steinhardt <ps@pks.im> --- Documentation/CodingGuidelines | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/CodingGuidelines b/Documentation/CodingGuidelines index b63a8f9a44..3daa1f82bb 100644 --- a/Documentation/CodingGuidelines +++ b/Documentation/CodingGuidelines @@ -244,7 +244,7 @@ For C programs: . since around 2007 with 2b6854c863a, we have been using initializer elements which are not computable at load time. E.g.: - const char *args[] = {"constant", variable, NULL}; + const char *args[] = { "constant", variable, NULL }; . since early 2012 with e1327023ea, we have been using an enum definition whose last element is followed by a comma. This, like
-- 2.46.0.dirty