Ariel Ben-Yehuda

Are there that many extern C function to cause a serious size cost? Could you have a test that checks for the expected runtime behavior?

> Am I correct in thinking that there will be no cost if built with panic=abort, it will still abort immediately? This PR does not affect panic=abort since panic=abort has...

I'll just note that `block_in_place` does not take a *future* but rather a synchronous function, and I expect this API will also take one.

> Would the static need to be re-exported from the higher level crate, or can I just add `tokio-rustls` to my `Cargo.toml` (with appropriate features etc) and grab it myself...

> @arielb1 currently in the sample code, it accepts async and blocks on it inside of block_in_place to allow async execution. The API of [block_in_place] is sync, so you mean...

> Yeah that's what I was worried about. If versions are the same it should be the same compiled lib and therefore the same static, but wasn't sure if that...

Maybe we should have a rustls-heavy-futures-executor crate with 1 major version that rustls depends on?On 6 Dec 2024, at 12:49, jclmnop ***@***.***> wrote: Instead, since we aren't allocating anything to...