Add binding for GIT_OPT_SET_CACHE_OBJECT_LIMIT

Author: qaqland

src/opts.rs

@@ -5,7 +5,7 @@ use std::ptr;
 
 use crate::string_array::StringArray;
 use crate::util::Binding;
-use crate::{raw, Buf, ConfigLevel, Error, IntoCString};
+use crate::{raw, Buf, ConfigLevel, Error, IntoCString, ObjectType};
 
 /// Set the search path for a level of config data. The search path applied to
 /// shared attributes and ignore files, too.
@@ -89,6 +89,25 @@ pub fn enable_caching(enabled: bool) {
     debug_assert!(error >= 0);
 }
 
+/// Set the maximum data size for the given type of object to be considered
+/// eligible for caching in memory.  Setting to value to zero means that that
+/// type of object will not be cached.  Defaults to 0 for [`ObjectType::Blob`]
+/// (i.e. won't cache blobs) and 4k for [`ObjectType::Commit`],
+/// [`ObjectType::Tree`], and [`ObjectType::Tag`].
+pub fn set_cache_object_limit(kind: ObjectType, size: libc::size_t) {
+    crate::init();
+    let error = unsafe {
+        raw::git_libgit2_opts(
+            raw::GIT_OPT_SET_CACHE_OBJECT_LIMIT as libc::c_int,
+            kind as libc::c_int,
+            size,
+        )
+    };
+    // This function cannot actually fail, but the function has an error return
+    // for other options that can.
+    debug_assert!(error >= 0);
+}
+
 /// Controls whether or not libgit2 will verify when writing an object that all
 /// objects it references are valid. Enabled by default, but disabling this can
 /// significantly improve performance, at the cost of potentially allowing the