fix: be stricter when initializing

A size < 0 is not valid and causes runtime panics when setting items. Panicking earlier with a clearer message avoids more subtle erroneous usage.

Author: costela

s3fifo/s3fifo.go

@@ -44,8 +44,7 @@ type S3FIFO[K comparable, V any] struct {
 	buckets []bucket[K, V]
 
 	// ttl is the time to live of the cache entry
-	ttl        time.Duration
-	ttlEnabled bool
+	ttl time.Duration
 
 	// nextCleanupBucket is an index of the next bucket to be cleaned up
 	nextCleanupBucket int8

sieve/sieve.go

@@ -43,8 +43,7 @@ type Sieve[K comparable, V any] struct {
 	buckets []bucket[K, V]
 
 	// ttl is the time to live of the cache entry
-	ttl        time.Duration
-	ttlEnabled bool
+	ttl time.Duration
 
 	// nextCleanupBucket is an index of the next bucket to be cleaned up
 	nextCleanupBucket int8
@@ -62,6 +61,10 @@ func New[K comparable, V any](size int, ttl time.Duration) *Sieve[K, V] {
 		ttl = 0
 	}
 
+	if size <= 0 {
+		panic("sieve: size must be greater than 0")
+	}
+
 	cache := &Sieve[K, V]{
 		ctx:               ctx,
 		cancel:            cancel,