mirror of
https://github.com/git/git.git
synced 2025-12-05 18:47:16 -06:00
f366bfe16b
The varint subsystem currently uses implicit widths for integers. On the one hand we use `uintmax_t` for the actual value. On the other hand, we use `int` for the length of the encoded varint. Both of these have known maximum values, as we only support at most 16 bytes when encoding varints. Thus, we know that we won't ever exceed `uint64_t` for the actual value and `uint8_t` for the prefix length. Refactor the code to use explicit widths. Besides making the logic platform-independent, it also makes our life a bit easier in the next commit, where we reimplement "varint.c" in Rust. Suggested-by: Ezekiel Newren <ezekielnewren@gmail.com> Signed-off-by: Patrick Steinhardt <ps@pks.im> Signed-off-by: Junio C Hamano <gitster@pobox.com>
8 lines
156 B
C
8 lines
156 B
C
#ifndef VARINT_H
|
|
#define VARINT_H
|
|
|
|
uint8_t encode_varint(uint64_t, unsigned char *);
|
|
uint64_t decode_varint(const unsigned char **);
|
|
|
|
#endif /* VARINT_H */
|