]> git.ipfire.org Git - thirdparty/git.git/commit
projects / thirdparty / git.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 34b6ce9) | patch
CodingGuidelines: discourage arbitrary suffixes in function names
authorKarthik Nayak <karthik.188@gmail.com>
Thu, 24 Oct 2024 10:53:57 +0000 (12:53 +0200)
committerTaylor Blau <me@ttaylorr.com>
Thu, 24 Oct 2024 16:51:30 +0000 (12:51 -0400)
commitbe75cec1b62b9f873c7fc50bbaff3002d82ab458
tree00084fe2cf48a3e4281c65ddf56881fa76cb1b31tree | snapshot
parent34b6ce9b30747131b6e781ff718a45328aa887d0commit | diff
CodingGuidelines: discourage arbitrary suffixes in function names

We often name functions with arbitrary suffixes like `_1` as an
extension of another existing function. This creates confusion and
doesn't provide good clarity into the functions purpose. Let's document
good function naming etiquette in our CodingGuidelines.

Signed-off-by: Karthik Nayak <karthik.188@gmail.com>
Signed-off-by: Taylor Blau <me@ttaylorr.com>
Documentation/CodingGuidelines diff | blob | blame | history
Unnamed repository; edit this file 'description' to name the repository.