While users of the reftable library wouldn't generally require access to individual blocks in a reftable table, there are valid usecases where one may require low-level access to them. One such upcoming usecase in the Git codebase is to implement consistency checks for the reftable library where we want to verify each block individually. Create a public interface for reading blocks. The interface isn't yet complete and lacks e.g. a way to read individual records from a block. Such missing functionality will be backfilled in subsequent commits. Note that this change also requires us to expose `reftable_buf`, which is used by the `reftable_block_first_key()` function. Signed-off-by: Patrick Steinhardt <ps@pks.im> Signed-off-by: Junio C Hamano <gitster@pobox.com>
40 lines
1.0 KiB
C
40 lines
1.0 KiB
C
/*
|
|
* Copyright 2020 Google LLC
|
|
*
|
|
* Use of this source code is governed by a BSD-style
|
|
* license that can be found in the LICENSE file or at
|
|
* https://developers.google.com/open-source/licenses/bsd
|
|
*/
|
|
|
|
#ifndef REFTABLE_BASICS_H
|
|
#define REFTABLE_BASICS_H
|
|
|
|
#include <stddef.h>
|
|
|
|
/* A buffer that contains arbitrary byte slices. */
|
|
struct reftable_buf {
|
|
size_t alloc;
|
|
size_t len;
|
|
char *buf;
|
|
};
|
|
#define REFTABLE_BUF_INIT { 0 }
|
|
|
|
/*
|
|
* Hash functions understood by the reftable library. Note that the values are
|
|
* arbitrary and somewhat random such that we can easily detect cases where the
|
|
* hash hasn't been properly set up.
|
|
*/
|
|
enum reftable_hash {
|
|
REFTABLE_HASH_SHA1 = 89,
|
|
REFTABLE_HASH_SHA256 = 247,
|
|
};
|
|
#define REFTABLE_HASH_SIZE_SHA1 20
|
|
#define REFTABLE_HASH_SIZE_SHA256 32
|
|
#define REFTABLE_HASH_SIZE_MAX REFTABLE_HASH_SIZE_SHA256
|
|
|
|
/* Overrides the functions to use for memory management. */
|
|
void reftable_set_alloc(void *(*malloc)(size_t),
|
|
void *(*realloc)(void *, size_t), void (*free)(void *));
|
|
|
|
#endif
|