aboutsummaryrefslogtreecommitdiff
path: root/varint.h
diff options
context:
space:
mode:
authorPatrick Steinhardt <ps@pks.im>2025-10-02 09:29:30 +0200
committerJunio C Hamano <gitster@pobox.com>2025-10-02 09:32:32 -0700
commitf366bfe16b350240c70c487d180c76ddcb8a1b2d (patch)
tree8300e3b1b91d01b75bf7a08fc5642a0eea04302a /varint.h
parentcb2badb4db67bcd02cc99a336c7b6bb0281980a1 (diff)
downloadgit-f366bfe16b350240c70c487d180c76ddcb8a1b2d.tar.xz
varint: use explicit width for integers
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>
Diffstat (limited to 'varint.h')
-rw-r--r--varint.h4
1 files changed, 2 insertions, 2 deletions
diff --git a/varint.h b/varint.h
index f78bb0ca52..eb401935bd 100644
--- a/varint.h
+++ b/varint.h
@@ -1,7 +1,7 @@
#ifndef VARINT_H
#define VARINT_H
-int encode_varint(uintmax_t, unsigned char *);
-uintmax_t decode_varint(const unsigned char **);
+uint8_t encode_varint(uint64_t, unsigned char *);
+uint64_t decode_varint(const unsigned char **);
#endif /* VARINT_H */