David Barsky

> Could you also consider the use-case where you need to have different filters for different writers? I want to report only WARN+ logs in human-readable format to stderr while...

Am I correct in understanding that this API doesn't prevent the usage of `tracing-core` in `#[no_std]` + no `alloc` environments? It seems like the construction of `DynCollect` only has dependencies...

Typed headers exist at [hyperium/headers](https://github.com/hyperium/headers), and they can be used with the latest releases of `hyperium/http` & `hyperium/hyper`—you might not need to write your own bridging.

It’s not well advertised, and it requires importing an extension trait so that the `http::header::HeaderMap` can use the typed headers. The derive headers in the repository only supports headers defined...

@dastbe: > For #1707 and #1696 , is this solving the problems defined there by helping you generate a general HTTP request from an Input which you could then pass...

@swarmer That's one possible variant. I was also thinking of passing the service name, region, and the `http::Request` to the signer directly as arguments. --- @dastbe > @davidbarsky Ah, so...

I spoke to @iliana last week, but I didn't get the change to write up the summary of our discussion until now. @iliana mentioned that Rusoto has a hard dependency...

I also want to link to [this very good Reddit comment](https://www.reddit.com/r/rust/comments/fnj12j/rust_async_and_the_terrible_horrible_no_good_very/flao3k9?utm_source=share&utm_medium=web2x) by @Matthias247 on splitting reactors/executors: > I agree that it would be nice to decouple components as much as...

@kennetpostigo Yes, among other changes, this proposal would allow Rusoto users to pick the runtime and networking library.

> At this point this PR is a bugfix and should get prioritized. @zoonman I don't believe that there's any maintainer of Rusoto left, as most people have left Amazon...