|
This may have been answered previously, but I couldn’t
find it in the archives… I am using an ArraySink to hold a resulting buffer of bytes generated
by a chain of transformations. I would like to be able to keep the results
after the lifetime of the ArraySink ends, but I see that the crypto policy is
to manage any pointer objects for me. This will require me to copy the buffer,
which may be reasonably large, and seems wasteful regardless. I don’t see
a reference overload of the ArraySink constructor; is there another sink that
would serve my purpose? |
