@elizarov at the end of your talk you mention that you’re working on an IO library - is that work happening in the open anywhere?

@cy is working on that

@cy can you talk about this?

@kevinherron sure

Openly? Do you need users or contributors?

the plan is to fold it into

kotlinx.corouties

. It is currently in a separate branch, pending review and merge: https://github.com/Kotlin/kotlinx.coroutines/pull/99

will there eventually be a

SocketChannel

or some such implementation or is this intended to be a buffers only?

There will be an ability to connect channel to a socket (a channel for reading, a channel for writing). They will be always buffered, e.g. write a bunch of data to channel, then flush, then it goes to socket.

any chance it will be a socket abstraction rather than a

java.net.Socket

? I have this dream of doing network I/O in coroutine-based pure Kotlin that can at some point be multiplatform rather than JVM-specific…

We don’t plan to expose java.net.Socket, because it is all riddled with blocking APIs

I have a lot of backend network code and protocol stack implementations. Right now I use netty, but I’d love to be able to move to pure Kotlin + coroutines, and as a bonus have the possibility to write the protocol stacks in a multi-platform compatible manner

Yes. That is exactly why we are undertaking this effort. For cross-platformness, that is. This way, we plan to be able to share all protocol code between platforms

fantastic. I’d like to help in any way possible, even if it’s just being an early adopter/tester