Repository is almost 450MB #1497
Labels
release item: 🔨 further change
solution: duplicate
the issue is a duplicate; refer to the linked issue instead
solution: proposed fix
a fix for the issue has been proposed and waits for confirmation
Milestone
The size of this repository is 436MB unpacked (although the download is 'only' ~150MB), which is insane for a tiny JSON parsing library. There are multiple cases where (IMO) the size can be trimmed down massively without actually impacting the repo.
The
.git
directory is 178MB, likely since you have a lot of changed binary files. You can easily slash the size of this directory by ~90% usinggit repack
(which has drawbacks for repo history, but unless you really care about specific info about changes from years ago this is fine).Why do you have a 23MB file of 1000000 signed integers in
test/data/regression/signed_ints.json
Do any of those ints besides the first few thousand really contribute any code coverage? I'd wager not. If the purpose of that many is to make sure the program can handle really large JSON files, why is there also another 23MB of unsigned integers? And 22MB of floats? Having lots of tests is good but this is seriously affecting users with slow internet speed who want to contribute to the project.The text was updated successfully, but these errors were encountered: