"Derrick Stolee via GitGitGadget" <gitgitgadget@xxxxxxxxx> writes:
> list is NULL as that does the same as ensure_full_index(). In fact,
> ensure_full_index() is converted to a shim over
> expand_to_pattern_list().
Sounds like a natural evolution of the API that used to be
all-or-none to expand-only-those-that-match.
The old one had a sensible name to tell us that it is about the
in-core index (and "full index" implied it was about sparse-index
feature because what state other than "full" the index can be---some
are shrunk into tree entries, which by definition is the
sparse-index feature). Contrasted to that, the name of the new one
is horrible. It does not even have index anywhere in the name.
I wonder expand_index() would work?
> +void expand_to_pattern_list(struct index_state *istate,
> + struct pattern_list *pl)
> {
> int i;
> struct index_state *full;
> struct strbuf base = STRBUF_INIT;
>
> + /*
> + * If the index is already full, then keep it full. We will convert
> + * it to a sparse index on write, if possible.
> + */
> if (!istate || !istate->sparse_index)
> return;
>
> + /*
> + * If our index is sparse, but our new pattern set does not use
> + * cone mode patterns, then we need to expand the index before we
> + * continue. A NULL pattern set indicates a full expansion to a
> + * full index.
> + */
> + if (pl && !pl->use_cone_patterns)
> + pl = NULL;
> +
> if (!istate->repo)
> istate->repo = the_repository;
>
> - trace2_region_enter("index", "ensure_full_index", istate->repo);
> + /*
> + * A NULL pattern set indicates we are expanding a full index, so
> + * we use a special region name that indicates the full expansion.
> + * This is used by test cases, but also helps to differentiate the
> + * two cases.
> + */
Except that we lost the distinction for non-cone mode, which I am
not sure matters, but I suspect we do not have to, if we do not want
to. Nobody used "pl" up to this point, so resetting it to NULL can
be done much later. In later phases of this series, we add another
case where we can lose pl even if we are not using cone mode, so
this distinction may start to matter later. I dunno.
I'd invent a separate "const char *tr2_region_label" variable and
set it at the beginning, regardless of where we clobber pl and why,
and use that label variable for trace2 calls, if I were doing this
patch. That feels much simpler and cleaner.
> + trace2_region_enter("index",
> + pl ? "expand_to_pattern_list" : "ensure_full_index",
> + istate->repo);
> diff --git a/sparse-index.h b/sparse-index.h
> index 633d4fb7e31..037b541f49d 100644
> --- a/sparse-index.h
> +++ b/sparse-index.h
> @@ -23,4 +23,18 @@ void expand_to_path(struct index_state *istate,
> struct repository;
> int set_sparse_index_config(struct repository *repo, int enable);
>
> +struct pattern_list;
> +
> +/**
> + * Scan the given index and compare its entries to the given pattern list.
> + * If the index is sparse and the pattern list uses cone mode patterns,
> + * then modify the index to contain the all of the file entries within that
> + * new pattern list. This expands sparse directories only as far as needed.
> + *
> + * If the pattern list is NULL or does not use cone mode patterns, then the
> + * index is expanded to a full index.
> + */
> +void expand_to_pattern_list(struct index_state *istate,
> + struct pattern_list *pl);
> +
> #endif
