Thank you @fukua95, will review as soon as possible.

@fukua95 we will have a discussion next week, overall I think the PR looks good, if the team agrees on the return types, I will merge this, thank you.

@fukua95 we will have a discussion next week, overall I think the PR looks good, if the team agrees on the return types, I will merge this, thank you.

Thank you for your review.

If there is anything that needs to be updated (the return types or others), please feel free to let me know.

One more thing: The VSim command in Redis code (unstable) has the option Epsilon, by the doc in Redis.io don't have. I'll modify the code after you decide whether to keep this option.

@fukua95 we are still not set on the return types, but one thing I will suggest is to use something similar to

@fukua95 we are still not set on the return types, but one thing I will suggest is to use something similar to

go-redis/sortedset_commands.go

Line 728 in 27581fc

type Z struct {

for the responses with scores. It will make this more consistent with the rest of the library and in general I don't see the benefit of having a map here - I don't see a lot of usecases that will benefit from the constant time to access an element. WDYT?

Using a struct is more user-friendly. I will update it soon.