git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v2 2/8] sha1-array: Implement oid_array_readonly_contains

From
SZEDER Gábor <szeder.dev@gmail.com>
Date
Jan 28, 2019, 13:05 UTC
Message-ID
<20190128130513.GA12887@szeder.dev>
In-Reply-To
<20190127194128.161250-2-sxenos@google.com>
On Sun, Jan 27, 2019 at 11:41:22AM -0800, sxenos@google.com wrote:
Show 33 quoted lines
> From: Stefan Xenos <sxenos@gmail.com>
> 
> Implement a "readonly_contains" function for oid_array that won't
> sort the array if it is unsorted. This can be used to test containment in
> the rare situations where the array order matters.
> 
> The function has intentionally been given a name that is more cumbersome
> than the "lookup" function, which is what most callers will will want
> in most situations.
> 
> Signed-off-by: Stefan Xenos <sxenos@google.com>
> ---
>  sha1-array.c               | 15 +++++++++++++++
>  sha1-array.h               |  2 ++
>  t/helper/test-sha1-array.c |  6 ++++++
>  t/t0064-sha1-array.sh      | 22 ++++++++++++++++++++++
>  4 files changed, 45 insertions(+)
> 
> diff --git a/sha1-array.c b/sha1-array.c
> index b94e0ec0f5..071fce7e90 100644
> --- a/sha1-array.c
> +++ b/sha1-array.c
> @@ -26,6 +26,21 @@ static const unsigned char *sha1_access(size_t index, void *table)
>  	return array[index].hash;
>  }
>  
> +int oid_array_readonly_contains(const struct oid_array* array,
> +	const struct object_id* oid)
> +{
> +	int i;
> +	if (array->sorted) {
> +		return sha1_pos(oid->hash, array->oid, array->nr, sha1_access) >= 0;
> +	}

Style nit: unnecessary braces. According to CodingGuidelines we tend not to use braces when the body of a loop or if statement is only a single line.

> +	for (i = 0; i < array->nr; i++) {
> +		if (hashcmp(array->oid[i].hash, oid->hash) == 0) {
Please use oideq() instead.
Show 9 quoted lines
> +			return 1;
> +		}
> +	}
> +	return 0;
> +}
> +
>  int oid_array_lookup(struct oid_array *array, const struct object_id *oid)
>  {
>  	if (!array->sorted)
Show 11 quoted lines
> diff --git a/t/t0064-sha1-array.sh b/t/t0064-sha1-array.sh
> index 5dda570b9a..c1bac6fcdd 100755
> --- a/t/t0064-sha1-array.sh
> +++ b/t/t0064-sha1-array.sh
> @@ -32,6 +32,28 @@ test_expect_success 'ordered enumeration with duplicate suppression' '
>  	test_cmp expect actual
>  '
>  
> +test_expect_success 'readonly_contains finds existing' '
> +	echo 1 > expect &&
> +	echoid "" 88 44 aa 55 >> expect &&
Style nit: not space between redirection operator and filename.
Show 25 quoted lines
> +	{
> +		echoid append 88 44 aa 55 &&
> +		echoid readonly_contains 55 &&
> +		echo for_each
> +	} | test-tool sha1-array >actual &&
> +	test_cmp expect actual
> +'
> +
> +test_expect_success 'readonly_contains non-existing query' '
> +	echo 0 > expect &&
> +	echoid "" 88 44 aa 55 >> expect &&
> +	{
> +		echoid append 88 44 aa 55 &&
> +		echoid readonly_contains 33 &&
> +		echo for_each
> +	} | test-tool sha1-array >actual &&
> +	test_cmp expect actual
> +'
> +
>  test_expect_success 'lookup' '
>  	{
>  		echoid append 88 44 aa 55 &&
> -- 
> 2.20.1.495.gaa96b0ce6b-goog
> 
Previous: sxenos@google.comNext: sxenos@google.com
Message 3 of 11 in “technical doc: add a design doc for the evolve command”
  1. 1/8 technical doc: add a design doc for the evolve commandsxenos@google.com, Jan 27, 2019
  2. 2/8 sha1-array: Implement oid_array_readonly_containssxenos@google.com, Jan 27, 2019
  3. SZEDER GáborJan 28, 2019
  4. 3/8 ref-filter: Add the metas namespace to ref-filtersxenos@google.com, Jan 27, 2019
  5. 4/8 evolve: Add support for parsing metacommitssxenos@google.com, Jan 27, 2019
  6. 5/8 evolve: Add the change-table structuresxenos@google.com, Jan 27, 2019
  7. 6/8 evolve: Add support for writing metacommitssxenos@google.com, Jan 27, 2019
  8. SZEDER GáborJan 29, 2019
  9. 7/8 evolve: Implement the git change commandsxenos@google.com, Jan 27, 2019
  10. 8/8 evolve: Add the git change list commandsxenos@google.com, Jan 27, 2019
  11. SZEDER GáborJan 29, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.