[PATCH 1/4] chainlint: add explanatory comments
- From
Eric Sunshine via GitGitGadget <gitgitgadget@gmail.com>
- Date
- Nov 8, 2022, 19:08 UTC
- Message-ID
- <a445304594c6139770439c49cf18f10c6757cbab.1667934510.git.gitgitgadget@gmail.com>
- In-Reply-To
- <pull.1375.git.git.1667934510.gitgitgadget@gmail.com>
From: Eric Sunshine <sunshine@sunshineco.com>
The logic in TestParser::accumulate() for detecting broken &&-chains is mostly well-commented, but a couple branches which were deemed obvious and straightforward lack comments. In retrospect, though, these cases may give future readers pause, so comment them, as well.
Signed-off-by: Eric Sunshine <sunshine@sunshineco.com> --- t/chainlint.pl | 4 ++++ 1 file changed, 4 insertions(+)
diff --git a/t/chainlint.pl b/t/chainlint.pl index 976db4b8a01..9908de6c758 100755 --- a/t/chainlint.pl +++ b/t/chainlint.pl @@ -505,7 +505,11 @@ my @safe_endings = ( sub accumulate { my ($self, $tokens, $cmd) = @_; + + # no previous command to check for missing "&&" goto DONE unless @$tokens; + + # new command is empty line; can't yet check if previous is missing "&&" goto DONE if @$cmd == 1 && $$cmd[0] eq "\n"; # did previous command end with "&&", "|", "|| return" or similar?
-- gitgitgadget