Patrick Steinhardt ee610b535c oidtree: add ability to store data ...

The oidtree data structure is currently only used to store object IDs,
without any associated data. So consequently, it can only really be used
to track which object IDs exist, and we can use the tree structure to
efficiently operate on OID prefixes.

But there are valid use cases where we want to both:

  - Store object IDs in a sorted order.

  - Associated arbitrary data with them.

Refactor the oidtree interface so that it allows us to store arbitrary
payloads within the respective nodes. This will be used in the next
commit.

Signed-off-by: Patrick Steinhardt <ps@pks.im>
Signed-off-by: Junio C Hamano <gitster@pobox.com>

2026-04-09 11:17:08 -07:00

..

clar

Merge branch 'ps/clar-wo-path-max'

2026-03-24 12:31:32 -07:00

.gitignore

…

generate-clar-decls.sh

…

generate-clar-suites.sh

…

lib-oid.c

…

lib-oid.h

…

lib-reftable.c

…

lib-reftable.h

…

test-lib.c

…

test-lib.h

…

u-ctype.c

…

u-dir.c

…

u-example-decorate.c

…

u-hash.c

…

u-hashmap.c

…

u-list-objects-filter-options.c

…

u-mem-pool.c

…

u-oid-array.c

…

u-oidmap.c

…

u-oidtree.c

oidtree: add ability to store data

2026-04-09 11:17:08 -07:00

u-prio-queue.c

…

u-reftable-basics.c

…

u-reftable-block.c

…

u-reftable-merged.c

…

u-reftable-pq.c

…

u-reftable-readwrite.c

…

u-reftable-record.c

…

u-reftable-stack.c

…

u-reftable-table.c

…

u-reftable-tree.c

…

u-strbuf.c

…

u-strcmp-offset.c

…

u-string-list.c

…

u-strvec.c

…

u-trailer.c

…

u-urlmatch-normalization.c

…

u-utf8-width.c

…

unit-test.c

…

unit-test.h

…