@Krux02, `seq[byte]` deals with GC. And If I need to implement readInt for the stream for example, first of all I'll read seq of sizeof(int) bytes and then `copyMem` them into result. Too much overhead. I need the pointer and size pair to remove that overhead.
- async I/O API: why strings? vega
- Re: async I/O API: why strings? vega
- Re: async I/O API: why strings? endragor
- Re: async I/O API: why strings? Varriount
- Re: async I/O API: why strings? dom96
- Re: async I/O API: why strings? _tulayang
- Re: async I/O API: why strings? vega
- Re: async I/O API: why strings? vega
- Re: async I/O API: why strings? Krux02
- Re: async I/O API: why strings? vega
- Re: async I/O API: why strings? endragor
- Re: async I/O API: why strings? Krux02
- Re: async I/O API: why strings? OderWat
- Re: async I/O API: why strings? ka
- Re: async I/O API: why strings? _tulayang
- Re: async I/O API: why strings? vega
- Re: async I/O API: why strings? endragor
- Re: async I/O API: why strings? vega