There should be a Native IoBuffer constructor public about kotlinx-io HOT 3 CLOSED

First of all, one shouldn't allocate IoBuffer directly. A packet should be used instead in most cases. It's not clear for me whether it should be ByteReadPacket.viewOf(pointer, size) or IoBuffer.viewOf(pointer, size). For now I am thinking of the first option. The only case for the second is very specific performance critical corners.

CPointers were disabled due to iOS related issues with K/N compiler but should be enabled back soon.

from kotlinx-io.

I disagree,
IoBuffer is very usefull to write.

While ByteReadPacket.viewOf(pointer, size) can be used to read, it could not be used to write on the memory of the Cpointer, which is why I think IoBuffer.viewOf(pointer, size) is very needed.

from kotlinx-io.

We're rebooting the kotlinx-io development (see #131), all issues related to the previous versions will be closed. Consider reopening it if the issue remains (or the feature is still missing) in a new version.

from kotlinx-io.