Arpad Borsos

My concern is rather the overhead of locking and arc-ing all the time even though you never re-configure. I think the best way forward here would be to actually measure...

`time 0.2` pulls this in unconditionally, and is being used through actix and surf.

actix is waiting on a release for `net2`, `time` is also waiting on a release of `time 0.3`, but that in turn means everyone else needs to upgrade…

@ashwoods lets make this a proper initiative so we can design this properly. I don’t really want people to "fake" native-looking events just to get source context ;-)

I think this is fair to do. How would this look like in the end? Thus far the transports are designed as "fire and forget" and they should not block...

You can always return a `Future`, but document the requirements around that: * callers (the SDK Client / transport wrappers) don’t need to await/poll it, they can just ignore/drop it...

I’m able to reproduce, and just managed to have it segfault in gdb: ``` Thread 3 "reqwest-interna" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7ffff76d8640 (LWP 82620)] 0x00007ffff7d89f40 in...

I have looked through the code, and there is no indication that the user is not being correctly passed on. Can you give a minimal code example to reproduce?

To be fair, I think just `run: rustup install stable` and variations of that one, and similarly `run: cargo test` is way simpler than something based on an action. I...

I’m not really familiar with `rust-toolchain.toml` and how to best use that. For the projects I help maintain, we test against our MSRV, stable and beta, and have no requirements...