mirrors/arti.git/crates/tor-chanmgr/src/mgr.rs, branch arti-v1.2.7

extract tor_async_utils::oneshot into ::oneshot-fused-workaround

2024-08-28T14:27:46Z

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.

Make Channel non-Clone.

2024-05-16T16:24:12Z

proto: Make Channel explicitly Arc<.>

2024-05-16T16:24:12Z

Previously, Channel was a type that you could Clone that implicitly its state. Now, Channel always appears as an Arc. This change has several benefits: * It makes the relationship between Channel struct and the underlying channel more clear. * It enables Channel to participate in the RPC system, where everything has to be an Arc<.> * It enables us to have a Weak, if we ever want to. * It will let us move various members out of ChannelDetails. We did this change a while ago with ClientCirc.

Run maint/add_warning.

2024-03-13T16:30:53Z

oneshot: Apply deferred rustfmt churn

2023-10-11T15:19:46Z

cargo fmt, precisely.

oneshot: Use veneer in tor-chanmgr

2023-10-11T15:19:21Z

Run maint/add_warning to add lint block everywhere

2023-08-23T09:34:00Z

Merge branch 'clippy-allow' into 'main'

2023-07-11T09:37:42Z

clippy: Allow some of our existing code patterns See merge request tpo/core/arti!1396

rng ranges: Use gen_range_checked().expect() in obvious cases (fmt)

2023-07-10T15:07:18Z

rng ranges: Use gen_range_checked().expect() in obvious cases

2023-07-10T15:07:18Z

In each of these, it is locally obvious that the range is nonempty.