![]() ... this may be a no-op optimization, but well. It is actually trigger to do the right thing here. In this version we flush the `values` array, which transfers ownership of the array buffer to the RESPValue. But that buffer is never going to be modified, so it would be nice to keep it alive. But if we do keep it alive, we also keep the RESPValues alive, which may point to full ByteBuffer's, which is not desirable. Whatever you do in Swift, you loose ;-) |
||
---|---|---|
.. | ||
NIORedis | ||
Redis |