David Barsky

For our [Lambda runtime](https://github.com/awslabs/aws-lambda-rust-runtime), requests from Application Load Balancers and API Gateway come in as JSON blobs ([an example](https://aws.amazon.com/blogs/networking-and-content-delivery/lambda-functions-as-targets-for-application-load-balancers/), if you're curious). Some feature _along_ these lines would be nice,...

> For the record, I lightly disagree w/ @seanmonstar in that I consider the risk fairly low if the feature flag is not enabled by default. First, it would be...

@thomaseizinger At the risk of misspeaking on Sean's behalf, I think renaming this feature to be `serde1` is sufficient. I think other types in this crate can be handled in...

I've shared my opinion on `extensions` previously and it still hasn't changed. Short version: I think should be removed. Long version: - There are three logical parts of an `http::Request`:...

> The issue is that task/thread-locals don't work with most channel backed offtask clients like hyper and tower-buffer. While ext do work with this setup. They couple data that is...

@torkleyy Apologies for the delay. Yes, I think this should also apply to the derive macro.

@vorner I _think_ it’ll be okay to release a 0.2 without support for backtraces in std. At the very latest, I’d like to release Failure 0.2 before 1.33, which is...

With regard to deriving Error, I agree about the minimization of fragmentation ecosystem-wide. As a single data point, @sapessi ran into a lot of issues with the current Fail derive...

@spinda: I was thinking of renaming it to `DefaultError` with suggestions in the documentation to rename `failure::DefaultError` to `failure::Error` when `Error` is the application's catch-all. Feel free to take a...

@yoshuawuyts I responded to your comment on: https://github.com/rust-lang-nursery/failure/pull/296#issuecomment-456110251!