From 176fd23002293182c1927007fb01eff09962f754 Mon Sep 17 00:00:00 2001 From: Brian Anderson Date: Wed, 9 Mar 2022 15:07:51 -0600 Subject: [PATCH] Continue making it possible to implement RpcSender (#23561) * Make nonblocking RpcClient::new_sender pub As is the blocking RpcClient::new_sender, per #23503. * Make solana_client::rpc_sender pub Per #17631 it is supposed to be possible to implement RpcSender in order to call RpcClient::new_sender. As of now though it is not possible to name RpcSender in order to implement it. --- client/src/lib.rs | 2 +- client/src/nonblocking/rpc_client.rs | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/client/src/lib.rs b/client/src/lib.rs index 72cb649686..5be24dee1b 100644 --- a/client/src/lib.rs +++ b/client/src/lib.rs @@ -18,7 +18,7 @@ pub mod rpc_deprecated_config; pub mod rpc_filter; pub mod rpc_request; pub mod rpc_response; -pub(crate) mod rpc_sender; +pub mod rpc_sender; pub mod spinner; pub mod thin_client; pub mod tpu_client; diff --git a/client/src/nonblocking/rpc_client.rs b/client/src/nonblocking/rpc_client.rs index d62203d319..9cbef3f24f 100644 --- a/client/src/nonblocking/rpc_client.rs +++ b/client/src/nonblocking/rpc_client.rs @@ -148,7 +148,7 @@ impl RpcClient { /// `RpcSender`. Most applications should use one of the other constructors, /// such as [`new`] and [`new_mock`], which create an `RpcClient` /// encapsulating an [`HttpSender`] and [`MockSender`] respectively. - pub(crate) fn new_sender( + pub fn new_sender( sender: T, config: RpcClientConfig, ) -> Self {