mirrors/arti.git/crates/tor-async-utils/src/lib.rs, branch arti-v1.4.6 mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.4.6 2025-07-07T15:50:04Z Temporarily suppress mismatched_lifetime_syntaxes. 2025-07-07T15:50:04Z Gabriela Moldovan gabi@torproject.org 2025-07-07T15:50:04Z urn:sha1:a11b611466a5a73f5e06a0aabd17284a57d12fe3 See #2060. clippy: deny `mod_module_files` 2025-01-06T23:09:41Z Steven Engler opara@torproject.org 2025-01-06T23:02:49Z urn:sha1:252a3a803b2db65792db5bd51dee8950d8557e0d Denies 'mod.rs' files for consistency. https://rust-lang.github.io/rust-clippy/master/index.html#mod_module_files add_warnings, *: Allow clippy::needless_lifetimes 2024-12-03T14:27:26Z Nick Mathewson nickm@torproject.org 2024-12-03T14:15:50Z urn:sha1:64cc3f2ed3eea0b7c5cc89ae07cbdadfdc1646fb In 1.83, this warning triggers on many of our crates. We're thinking of fixing them all, but for now, we're going to disable the warning. This is part of #1765. Introduce mpsc_channel_no_memquota and use it in the places it's wanted 2024-10-15T10:52:34Z Ian Jackson ijackson@chiark.greenend.org.uk 2024-10-09T18:00:03Z urn:sha1:fe219904a9c70fc1c9079a88e9ecefb151ac47e4 These are the call sites where using this fucntion is correct. (Outside tor-rtmock, which we'll do separately.) Provide SinkCloseChannel 2024-10-01T18:18:04Z Ian Jackson ijackson@chiark.greenend.org.uk 2024-10-01T12:32:01Z urn:sha1:5bc156a063a2a9a447cefd4a24f8e35bac1f1e81 The circuit reactor calls mpsc::Channel::close_channel, but we want to wrap up the mpsc, so we need to make this a trait method. tor-async-utils: Implement SinkTrySend for mpsc::Sender 2024-10-01T17:29:40Z Ian Jackson ijackson@chiark.greenend.org.uk 2024-09-30T16:25:01Z urn:sha1:84286777c28f8e1827589377b2ee55c79db501db tor-async-utils: Provide new SinkTrySend trait 2024-10-01T17:29:40Z Ian Jackson ijackson@chiark.greenend.org.uk 2024-09-30T16:12:23Z urn:sha1:99c400a15cd449e5d4dd7eb44e9888d8a15c4a3f This is the method try_send from mpsc::channel::Sender. We want to be able to replace that type in tor-circmgr with a memquota wrapper, so the call needs to be a trait method. This API is deceptively simple. Implementing it will involve more support machinery for error handling. tor-async-utils: Re-export oneshot-fused-workaround as oneshot. 2024-09-03T15:05:19Z Gabriela Moldovan gabi@torproject.org 2024-09-03T15:05:19Z urn:sha1:4e9cf15afb86a4cb76898fd03c67a9a1cef0bd5d Move stream_peek into tor-async-utils 2024-08-29T14:08:06Z Jim Newsome jnewsome@torproject.org 2024-08-21T19:23:49Z urn:sha1:2a11886271c41a0e2449c944b2f24db7f243d506 extract tor_async_utils::oneshot into ::oneshot-fused-workaround 2024-08-28T14:27:46Z Jim Newsome jnewsome@torproject.org 2024-08-22T19:20:36Z urn:sha1:46f7f01092e6ac55e3e958dc3a2228b1d36e26a1 Having this in the `tor-async-utils` crate prevents us from doing both of the following without introducing a circular dependency: * using it in `tor-rtmock` (which we currently do, particularly in tests). * using `tor-rtmock` to test things in `tor-async-utils`. We don't do this yet, but it is generally sensible to do so. In particular we want to move the `stream_peak` module there, which is currently tested with `tor-rtmock`. Moving this into its own crate avoids this circular dependency.