John-John Tedro

Adding this as an enhancement, it's a low hanging fruit if someone wants to pick it up.

FFWD's http support is a non-blocking implementation from https://github.com/igrigorik/em-http-request - so blocking itself is not a huge issue as long as datadog can handle the supplied load and responds within...

Thanks. I do have one minor minorly related questions if you don't mind. I can't find serde support for serializing with existing buffers, which makes the serde-based benchmarks much slower...

All right, so I'll put the serde-based tests in a separate category too :) I'm guessing then this also extends to fields marked with `#[bitcode(with_serde)]`, as in additional internal allocations...

Hey, thanks for the kind words. Sure, it and its dependencies could be punted behind a feature flag. Or even a separate crate (as proven by being in the examples...

It depends on the service, with for example Twitch [you send a `Authorization: Bearer ` header for each request](https://dev.twitch.tv/docs/authentication#sending-user-access-and-app-access-tokens).

You get the access token through [Token::access_token](https://docs.rs/async-oauth2/latest/oauth2/trait.Token.html#tymethod.access_token) which derefs to `str`, so it can be used as a string. So like this: ```rust use oauth2::Token; let token = /* */;...

Right! All of them should be able to, [an example is provided for musli-json](https://github.com/udoprog/musli/blob/main/crates/no-std-examples/examples/no-std-json.rs), but the same pattern should be usable across all formats that provide `encode_with` and `from_slice_with`. *...

Would you mind providing a code example to better indicate what it is that you want to do?

Thanks! I just want to check in with you that this might unintentionally be storing more data than you need. This: ```rust #[derive(ZeroCopy)] #[repr(C)] struct TestValue { timestamp: u32, tag:...