From d3eaa1808fe1aeaa316d81fcde6ebb6079a3980e Mon Sep 17 00:00:00 2001
From: Runxi Yu
Date: Fri, 28 Nov 2025 08:00:00 +0800
Subject: hash: data after size

This guarantees ... I guess ABI stability of where the size is,
regardless of the version which may have different maxHashSize.
Not too useful but I guess good practice
---
 hash.go | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/hash.go b/hash.go
index 068eb840..3edb6079 100644
--- a/hash.go
+++ b/hash.go
@@ -10,8 +10,8 @@ const maxHashSize = 32
 
 // Hash represents a Git object ID.
 type Hash struct {
-	data [maxHashSize]byte
 	size int
+	data [maxHashSize]byte
 }
 
 // hashFunc is a function that computes a hash from input data.
-- 
cgit v1.3.1-10-gc9f91