Eugene Kabanov

But i can't find any descriptors leakage, but found a problem inside of your code. `server.join()` is waiting for somebody to call `server.close()`. So to stop and close server properly...

@nitely you will never get EOF if you will not perform read operation on closed socket, in such way EOF marker will be set.

@nitely i have found a problem, leakage happens because readUntil() generated exception `IncompleteError`, and because tasks are started without `asyncCheck` this exceptions got hidden.

@nitely what do you think about this benchmark https://gist.github.com/cheatfate/2a46181ab03f1a2dc2c943b3e1a56ca5

If you don't need that pointer, just don't use it, but i need it in streams and other places to avoid closure environment allocation.

If you do not want to have SSL bundled, just `import apps/http/httpserver`.

Here i want to show how to obtain `response` object, which can be used to obtain response headers. ```nim import chronos/apps/http/httpclient proc getClient() {.async.} = var session = HttpSessionRef.new({HttpClientFlag.NoVerifyHost, HttpClientFlag.NoVerifyServerName},...

And this is main difference between `std/httpclient` and `chronos.httpclient` because in both samples above, body has not been received yet, only response headers are obtained from the network.

This is very old known issue. Because `async` macro is working with `untyped` arguments its impossible to fix it properly. For example, if we are going to replace all unattended...

This is very bad idea, because all the implicit conversions of target procedure arguments or return value can create confusion when reading compiler's errors. Compiler will show you types which...