I was trying to avoid adding a function that doesn't reflect memcached's interface. I added 'gets' because I don't see a way to make 'get' return CAS while remaining backward-compatible, but it's possible to make 'set' support both scenarios.

Alternately, how do you feel about changing the signature of 'set' to support an optional (=0) 'cas' argument? This may break backward compatibility for the rare (I assume) users who use TTL and/or options, but it would closer reflect memcached's interface.