b8ca235ca5
The merged table provides access to a reftable stack by merging the contents of those tables into a virtual table. These subtables are being tracked via `struct reftable_table`, which is a generic interface for accessing either a single reftable or a merged reftable. So in theory, it would be possible for the merged table to merge together other merged tables. This is somewhat nonsensical though: we only ever set up a merged table over normal reftables, and there is no reason to do otherwise. This generic interface thus makes the code way harder to follow and reason about than really necessary. The abstraction layer may also have an impact on performance, even though the extra set of vtable function calls probably doesn't really matter. Refactor the merged tables to use a `struct reftable_reader` for each of the subtables instead, which gives us direct access to the underlying tables. Adjust names accordingly. Signed-off-by: Patrick Steinhardt <ps@pks.im> Signed-off-by: Junio C Hamano <gitster@pobox.com> |
||
|---|---|---|
| .. | ||
| .gitignore | ||
| lib-oid.c | ||
| lib-oid.h | ||
| t-ctype.c | ||
| t-example-decorate.c | ||
| t-hash.c | ||
| t-mem-pool.c | ||
| t-oidmap.c | ||
| t-oidtree.c | ||
| t-prio-queue.c | ||
| t-reftable-basics.c | ||
| t-reftable-merged.c | ||
| t-reftable-record.c | ||
| t-strbuf.c | ||
| t-strcmp-offset.c | ||
| t-strvec.c | ||
| t-trailer.c | ||
| test-lib.c | ||
| test-lib.h | ||