summaryrefslogtreecommitdiff
path: root/tor-rtcompat/Cargo.toml
Commit message (Collapse)AuthorAgeFilesLines
* Remove "publish = false"Nick Mathewson2021-06-241-1/+0
|
* Bump tokio-related dependenciesNick Mathewson2021-06-241-2/+2
|
* Remove some (but not all) needless dependencies.Nick Mathewson2021-06-171-1/+0
|
* Remove a redundant feature in tokioNick Mathewson2021-05-201-1/+1
|
* Implement Runtime for a thin wrapper around tokio runtime handlesNick Mathewson2021-05-201-1/+1
| | | | | Having this enables us to use Arti with an externally constructed tokio runtime.
* Give every Cargo.toml a repository fieldNick Mathewson2021-05-191-0/+1
|
* Split mocking parts of rtcompat into new rtmock crate.Nick Mathewson2021-05-031-5/+0
| | | | | Since these parts are testing-only, let's take steps to make sure we don't ship them in production by accident.
* bump to latest async_ioNick Mathewson2021-05-031-1/+1
|
* Add a MockNetwork structure for testing.Nick Mathewson2021-04-281-0/+1
| | | | | This isn't a shadow replacement: it's just a testing fixture that we can use to try out code that wants to connect and/or listen.
* Add a "socketpair"-style linked-reader/writer implementation for testingNick Mathewson2021-04-211-0/+3
|
* Begin a refactoring of tor-rtcompat to use runtime objects.Nick Mathewson2021-04-161-2/+4
| | | | | | | | So far, all traits are defined (I hope) and the task api is ported. With time I want to have none of the current "global runtime" APIs exposed, and just use Runtime objects instead. But that isn't just yet.
* Move responsibility for knowing about TLS into tor_rtcompat.Nick Mathewson2021-03-231-2/+6
| | | | Now we don't need runtime-specific stuff in tor-chanmgr.
* Refactor tokio implpementation in tor-rtcompat.Nick Mathewson2021-03-231-3/+6
| | | | | | | | | | | Now other crates don't need any 'ifdef tokio' code, since there are wrappers that implement 'futures' right. Technically, the 'futures' traits are in some ways less good than the tokio ones, but we need a consistent API if we want to support WASM someday and keep support for async_std. I'd rather hold out hope for a future version of futures::io working like tokio than to fix ourselves into the tokioverse forever.
* Add appropriate categories to some Cargo.toml files.Nick Mathewson2021-03-171-0/+1
|
* Add the tor project as an author.Nick Mathewson2021-03-171-1/+1
|
* Add keywords to each Cargo.tomlNick Mathewson2021-03-171-0/+1
|
* Add a description field to all our Cargo.toml filesNick Mathewson2021-03-171-0/+1
|
* Give it a homepage everyplace.Nick Mathewson2021-03-171-0/+1
|
* Cut down on tokio features.Nick Mathewson2021-03-101-1/+1
|
* Bump dependencies with "cargo upgrade"Nick Mathewson2021-03-061-1/+1
|
* Port to work with tokio or async-std.Nick Mathewson2021-03-021-1/+6
| | | | | | | | | | | | | | | | | | 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.
* Upgrade async-ioNick Mathewson2020-12-031-1/+1
|
* Bump to latest async-ioNick Mathewson2020-12-011-1/+1
|
* Remove a couple of unused dependenciesNick Mathewson2020-11-111-5/+0
|
* Isolate async_std usage in a new tor_rtcompat crate.Nick Mathewson2020-11-111-0/+23
Like tor_llcrypto, this crate is meant to expose only the part of other crates (in this case, a async runtime crate) that we use.