Size computation for allocation may overflow (#99)

* Size computation for allocation may overflow

Performing calculations involving the size of potentially large strings or slices can result in an overflow (for signed integer types) or a wraparound (for unsigned types). An overflow causes the result of the calculation to become negative, while a wraparound results in a small (positive) number.

vendor/github.com/redis/go-redis/v9/vectorset_commands.go

@@ -26,6 +26,7 @@ type VectorSetCmdable interface {
 	VSimWithScores(ctx context.Context, key string, val Vector) *VectorScoreSliceCmd
 	VSimWithArgs(ctx context.Context, key string, val Vector, args *VSimArgs) *StringSliceCmd
 	VSimWithArgsWithScores(ctx context.Context, key string, val Vector, args *VSimArgs) *VectorScoreSliceCmd
+	VRange(ctx context.Context, key, start, end string, count int64) *StringSliceCmd
 }
 
 type Vector interface {
@@ -345,3 +346,13 @@ func (c cmdable) VSimWithArgsWithScores(ctx context.Context, key string, val Vec
 	_ = c(ctx, cmd)
 	return cmd
 }
+
+// `VRANGE key start end count`
+// a negative count means to return all the elements in the vector set.
+// note: the API is experimental and may be subject to change.
+func (c cmdable) VRange(ctx context.Context, key, start, end string, count int64) *StringSliceCmd {
+	args := []any{"vrange", key, start, end, count}
+	cmd := NewStringSliceCmd(ctx, args...)
+	_ = c(ctx, cmd)
+	return cmd
+}