Paul Colomiets

Yes, it's fine. Any volunteers for a PR?

@colin-kiegel, do you accept the challenge? :)

That's my situation too. Hopefully, this is not a big deal for errors...

Probably it may look like: ``` quick_error! { #[derive(Debug)] pub enum ServerError { Io(error: io::Error) { wraps(error) } } } ``` I.e. the important thing it that it should be...

Yeah. I was thinking about using docstrings too. The issue is that we don't have a good parser for docstrings. This means we can either use all the lines in...

Well, it's not the problem with `tk-http` per se. But with the example code that does accepting connections. `buffer_unordered` exists on first error of the future. Which effectively means your...

Okay, so this piece of code seems to be quite large and useful not only for HTTP. I'm thinking to either put it into `tk-easyloop` or just create another crate...

Well, we don't use tokio-proto for protocol parsing for multiple reasons. So depending on it just for `listen` function doesn't look like a good idea. Also, the problem isn't solved...

Wow! While refactoring this example to a separate library I've found out that this code is a little bit wrong. When listening there are few errors that require sleep and...

So, I've published [tk-listen](https://crates.io/crates/tk-listen) crate. Probably, I'll update examples here to use the crate.