[PATCH v2] submodule-config: use hashmap_iter_first()

Subsystems: the rest

DORMANTno replies REVIEWED: 1 (0M)

1 review trailer.

4 messages, 4 authors, 2016-06-15 · open the first message on its own page

[PATCH v2] submodule-config: use hashmap_iter_first()

From: Alexander Kuleshov <hidden>
Date: 2016-06-15 23:08:45

from the <hashmap.h> for simplification.

Signed-off-by: Alexander Kuleshov <redacted>
Reviewed-by: Stefan Beller <redacted>
---
Changelog: added missed Signof-off-by and function name fixed
in the commit message.

 submodule-config.c | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/submodule-config.c b/submodule-config.c
index b82d1fb..8ac5031 100644
--- a/submodule-config.c
+++ b/submodule-config.c
@@ -405,8 +405,7 @@ static const struct submodule *config_from(struct submodule_cache *cache,
 		struct hashmap_iter iter;
 		struct submodule_entry *entry;
 
-		hashmap_iter_init(&cache->for_name, &iter);
-		entry = hashmap_iter_next(&iter);
+		entry = hashmap_iter_first(&cache->for_name, &iter);
 		if (!entry)
 			return NULL;
 		return entry->config;
-- 
2.8.0.rc2.216.g1477fb2.dirty

Re: [PATCH v2] submodule-config: use hashmap_iter_first()

From: Stefan Beller <hidden>
Date: 2016-06-15 23:08:45

On Tue, Mar 15, 2016 at 12:13 PM, Alexander Kuleshov
[off-list ref] wrote:
from the <hashmap.h> for simplification.
I think what Eric wanted to point out, was to not have a continuous sentence
from commit message header to body.

Either leave the body blank (as it is obvious) or write a whole sentence there:

  [PATCH v2] submodule-config: use hashmap_iter_first()

  The hashmap API offers the `hashmap_iter_first` function as initializing and
  getting the first entry is a common pattern. Use that instead of
doing initialization
  by hand and then get the first entry.


quoted hunk
Signed-off-by: Alexander Kuleshov <redacted>
Reviewed-by: Stefan Beller <redacted>
---
Changelog: added missed Signof-off-by and function name fixed
in the commit message.

 submodule-config.c | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/submodule-config.c b/submodule-config.c
index b82d1fb..8ac5031 100644
--- a/submodule-config.c
+++ b/submodule-config.c
@@ -405,8 +405,7 @@ static const struct submodule *config_from(struct submodule_cache *cache,
                struct hashmap_iter iter;
                struct submodule_entry *entry;

-               hashmap_iter_init(&cache->for_name, &iter);
-               entry = hashmap_iter_next(&iter);
+               entry = hashmap_iter_first(&cache->for_name, &iter);
                if (!entry)
                        return NULL;
                return entry->config;
--
2.8.0.rc2.216.g1477fb2.dirty

--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH v2] submodule-config: use hashmap_iter_first()

From: Eric Sunshine <hidden>
Date: 2016-06-15 23:08:45

On Tue, Mar 15, 2016 at 3:21 PM, Stefan Beller [off-list ref] wrote:
On Tue, Mar 15, 2016 at 12:13 PM, Alexander Kuleshov
[off-list ref] wrote:
quoted
from the <hashmap.h> for simplification.
I think what Eric wanted to point out, was to not have a continuous sentence
from commit message header to body.
Yes, thanks for clarifying that.
Either leave the body blank (as it is obvious) or write a whole sentence there:

  [PATCH v2] submodule-config: use hashmap_iter_first()

  The hashmap API offers the `hashmap_iter_first` function as initializing and
  getting the first entry is a common pattern. Use that instead of
doing initialization
  by hand and then get the first entry.

Re: [PATCH v2] submodule-config: use hashmap_iter_first()

From: Jeff King <hidden>
Date: 2016-06-15 23:08:45

On Tue, Mar 15, 2016 at 12:21:36PM -0700, Stefan Beller wrote:
On Tue, Mar 15, 2016 at 12:13 PM, Alexander Kuleshov
[off-list ref] wrote:
quoted
from the <hashmap.h> for simplification.
I think what Eric wanted to point out, was to not have a continuous sentence
from commit message header to body.

Either leave the body blank (as it is obvious) or write a whole sentence there:

  [PATCH v2] submodule-config: use hashmap_iter_first()

  The hashmap API offers the `hashmap_iter_first` function as initializing and
  getting the first entry is a common pattern. Use that instead of
doing initialization
  by hand and then get the first entry.
While we are nitpicking...:)

As a reader (either reviewing now, or looking at the change later in
git-log), I think my biggest question is: why?  Do we expect this to
change behavior, or is this just a cleanup? There's nothing wrong with
"just" a cleanup, but knowing that is the intent is helpful.

-Peff
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help