Re: async I/O API: why strings?

[Varriount]

This actually puzzles me too, especially since Nim are particularly inefficient 
for this kind of work (strings are copy-on-assignment, meaning the data is 
going to be copied at least twice on its way to a socket)