While I appreciate the work you put into this, as noted in #106, defining behaviour here where it is undefined upstream (in the redis ruby adapter) is somewhat dangerous; I would be more inclined to guard against receiving nil as a key (e.g., raise an ArgumentError) than to formalize the observed behaviour. I'm closing this PR for now, but leaving #106 open so we can decide what to do with unexpected input.