git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: Matheus Tavares <matheus.bernardino@usp.br>
Cc: Elijah Newren <newren@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] clean: remove unnecessary variable
Date: Thu, 6 May 2021 16:03:22 -0400	[thread overview]
Message-ID: <YJRLim10cznG5G3d@coredump.intra.peff.net> (raw)
In-Reply-To: <4f88ac58e46782c7cf335e13fabd14c8b4438267.1620329445.git.matheus.bernardino@usp.br>

On Thu, May 06, 2021 at 04:33:15PM -0300, Matheus Tavares wrote:

> The variable `matches` used to hold the return of a `dir_path_match()`
> call that was removed in 95c11ecc73 ("Fix error-prone fill_directory()
> API; make it only return matches", 2020-04-01). Now `matches` will
> always hold 0, which is the value it's initialized with; and the
> condition `matches != MATCHED_EXACTLY` will always evaluate to true. So
> let's remove this unnecessary variable.
>
> Interestingly, it seems that `matches != MATCHED_EXACTLY` was already
> unnecessary before 95c11ecc73. That's because `remove_directories` is
> always set to 1 when we have pathspecs; So, in the condition
> `!remove_directories && matches != MATCHED_EXACTLY`, we would either:
> 
> - have pathspecs (or have been given `-d`) and ignore `matches` because
>   `remove_directories` is 1; or
> 
> - not have pathspecs (nor `-d`) and end up just checking that
>   `0 != MATCHED_EXACTLY`, as `matches` would never get reassigned
>   after its zero initialization (because there is no pathspec to match).

Thanks for this digging and the extra analysis. We can see from the
patch that this variable can't possibly be doing anything, but it is
always a comfort to see authors researching the source of the oddity and
explaining what they found.

I'm adding Elijah to the cc as an area expert, just in case he has any
other insight.

> diff --git a/builtin/clean.c b/builtin/clean.c
> index 995053b791..f6d7e8119c 100644
> --- a/builtin/clean.c
> +++ b/builtin/clean.c
> @@ -1003,7 +1003,6 @@ int cmd_clean(int argc, const char **argv, const char *prefix)
>  
>  	for (i = 0; i < dir.nr; i++) {
>  		struct dir_entry *ent = dir.entries[i];
> -		int matches = 0;
>  		struct stat st;
>  		const char *rel;
>  
> @@ -1013,8 +1012,7 @@ int cmd_clean(int argc, const char **argv, const char *prefix)
>  		if (lstat(ent->name, &st))
>  			die_errno("Cannot lstat '%s'", ent->name);
>  
> -		if (S_ISDIR(st.st_mode) && !remove_directories &&
> -		    matches != MATCHED_EXACTLY)
> +		if (S_ISDIR(st.st_mode) && !remove_directories)
>  			continue;
>  
>  		rel = relative_path(ent->name, prefix, &buf);

Definitely not necessary, but on a patch like this I'll sometimes
manually specify "-U4" (and I always have diff.interhunkcontext set to
"1") to show the complete code between the declaration and use. It makes
it even more obvious that the result is correct (though obviously
applying and compiling shows it, too). #gitlifehacks

-Peff

  reply	other threads:[~2021-05-06 20:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-06 19:33 [PATCH] clean: remove unnecessary variable Matheus Tavares
2021-05-06 20:03 ` Jeff King [this message]
2021-05-06 21:14   ` Matheus Tavares Bernardino
2021-05-06 21:35   ` Elijah Newren

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YJRLim10cznG5G3d@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=matheus.bernardino@usp.br \
    --cc=newren@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).