ZRange behavior does not match Redis when using a negative STOP argument

[sds]

ZRange behavior does not match Redis when using a negative STOP argument

[sinclairtarget]

Just checked—this definitely isn't an issue in version 0.17.1:

irb(main):001:0> $redis
=> #<MockRedis:0x007fda302407e0 @options={:scheme=>"redis", :host=>"", :port=>0, :path=>nil, :timeout=>5.0, :password=>nil, :db=>0, :time_class=>Time, :connect_timeout=>nil, :read_timeout=>nil, :write_timeout=>nil}, @db=#<MockRedis::PipelinedWrapper:0x007fda30240330 @db=#<MockRedis::TransactionWrapper:0x007fda30240380 @db=#<MockRedis::ExpireWrapper:0x007fda302403a8 @db=#<MockRedis::MultiDbWrapper:0x007fda30240588 @db_index=0, @prototype_db=#<MockRedis::Database:0x007fda30240538 @base=#<MockRedis:0x007fda302407e0 ...>, @data={}, @expire_times=[]>, @databases={0=>#<MockRedis::Database:0x007fda30240650 @base=#<MockRedis:0x007fda302407e0 ...>, @data={}, @expire_times=[]>}>>, @transaction_futures=[], @in_multi=false, @multi_block_given=false>, @pipelined_futures=[], @in_pipeline=false>>
irb(main):002:0> $redis.zadd('myzset', 10, 10)
=> true
irb(main):003:0> $redis.zadd('myzset', 20, 20)
=> true
irb(main):004:0> $redis.zadd('myzset', 30, 30)
=> true
irb(main):005:0> $redis.zrange('myzset', 0, -4)
=> []

[sds]

Fixed by #132. Thanks for the report!