I'm not sure why (after reading through so many `Resque.backend.store.some_redis_method`), but this was the first one to strike me as wrong in some way, a leaky abstraction and a regression of the work that has been done to isolate the backend and make it an opaque interface of its own (so a consumer could replace it with something that has real-life durable queueing semantics when they outgrow redis). That's not to say it's a blocker, but perhaps we need to figure out a direction in which to take it. I'd be willing to pair on figuring this out either before or after the merge.