Nick Mathewson 8c31418500 Port to work with tokio or async-std. ... This is fairly ugly and I think I'll need to mess around with the feature configuration a while until we get something that's pleasant to develop with. This still seems like a good idea, though, since we _will_ need to be executor-agnostic in the end, or we'll have no way to handle wasm or embedded environments. Later down the road, we'll probably want to use futures::Executor or futures::Spawn more than having global entry points in tor_rtcompat. That would probably make our feature story simpler. Tokio is the default now, since tokio seems to be more heavily used for performance-critical stuff. This patch breaks tests; the next one will fix them, albeit questionably.		2021-03-02 11:55:09 -05:00
..
src	Make authorities and fallbacks configurable.	2021-02-11 13:08:46 -05:00
Cargo.toml	Port to work with tokio or async-std.	2021-03-02 11:55:09 -05:00