mirrors/arti.git/crates/arti-client/examples/hook-tcp.rs, branch arti-v1.0.0mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.0.02022-06-24T13:23:38Zclippy: Consolidate many lints in maint/add_warning2022-06-24T13:23:38ZIan Jacksonijackson@chiark.greenend.org.uk2022-06-24T12:24:00Zurn:sha1:23c352b96bf07c981bb396fa34ce83e512ada0b2
Found these by disabling the nightly dbg macro special case. Now, we
have a mechanism for globally adding suppressions to tests, we can use
that instead.
clippy: Add standard test lint block to several examples2022-06-24T13:23:38ZIan Jacksonijackson@chiark.greenend.org.uk2022-06-24T12:17:02Zurn:sha1:d965dc3f709259fbe1f0f954dcae50ccd4201799rt-compat: Make all the individual runtime traits Clone+Send etc.2022-06-08T10:24:26ZIan Jacksonijackson@chiark.greenend.org.uk2022-06-06T17:49:35Zurn:sha1:3ba3b26842254cfd9033ea37b44b746895bcbd02
This will make it much more convenient for code that only wants one of
these traits (or a subset of them). This is a good thing to support
because it will allow us to use a ZST in places that do not need an
actual async runtime handle (typically, the runtime handle is needed
only for spawn).
Resolve the new `derive_partial_eq_without_eq` lint.2022-05-23T16:55:37ZNick Mathewsonnickm@torproject.org2022-05-23T16:32:31Zurn:sha1:546ae3000eb179aedc97de30b0ccdb1d45b93395
It's a little overzealous sometimes, but it's mostly to the good.
add udp to runtime2022-03-14T19:59:33Ztrinity-1686atrinity@deuxfleurs.fr2022-03-05T18:49:38Zurn:sha1:4a44ef56c0743775d49eca138a253f11e93c7a35arti-client: use PreferredRuntime by default, doc cleanups2022-02-28T16:41:13Zetator@eta.st2022-02-25T18:13:02Zurn:sha1:13ba0ea005ddd87bba2d53ab738ce948f031e1e8
This makes using the `PreferredRuntime` the first-class option inside
`arti-client`, freeing users who don't want to think about runtimes from
having to do so.
`TorClient::create_unbootstrapped` and `builder` now automatically
use this runtime, leaving only `builder_custom` for users who wish to
manually specify a runtime.
This lets us clean up the docs a lot: mentions of using custom runtimes
are now relegated to nearer the end of the crate-level documentation,
and we mostly just link to `tor_rtcompat`'s docs to explain more there.
Instead, we take some more time to explain how you use the builder API
to create clients synchronously.
Other doc cleanups included getting rid of the explanation of `TorAddr`
in the main crate-level doc; this is already well-documented elsewhere,
and is something users should discover organically later.
fixes arti#326
use runtime TlsProvider in tcp-hook example2022-02-25T12:42:14Ztrinity-1686atrinity@deuxfleurs.fr2022-02-25T12:42:14Zurn:sha1:f633276a913ef85ce11bf576a9882db997edb9ffFix typos2022-02-23T19:07:05ZDimitris Apostoloudimitris.apostolou@icloud.com2022-02-23T19:07:05Zurn:sha1:a3c1ba4b1ab6ad31ea846acb86558159e285cad2add one more comment to hook-tcp2022-02-23T17:00:35Ztrinity-1686atrinity@deuxfleurs.fr2022-02-23T17:00:35Zurn:sha1:078a91c591a2c9ade87388ca07f26c37b649cebdexamples/hook-tcp: add some comments, rework lifetimes a bit2022-02-23T13:59:03Zetator@eta.st2022-02-23T13:59:03Zurn:sha1:9960064720a74691490ad0c78f834018bdc84771
Try to make the `hook-tcp` example a bit easier to read by
adding/changing comments, and renaming the lifetimes for
`async_trait`-generated trait methods.