From: Matt Corallo <git@bluematt.me>
Date: Thu, 14 May 2020 01:25:51 +0000 (-0400)
Subject: Expose PeerHandleError::no_connection_possible
X-Git-Tag: v0.0.12~61^2
X-Git-Url: http://git.bitcoin.ninja/index.cgi?a=commitdiff_plain;h=refs%2Fheads%2F2020-05-pre-bindings-cleanups;p=rust-lightning

Expose PeerHandleError::no_connection_possible

Its just a trivial bool and already has docs on it, so seems like
an oversight
---

diff --git a/lightning/src/ln/peer_handler.rs b/lightning/src/ln/peer_handler.rs
index e6160b0e5..009fa73f9 100644
--- a/lightning/src/ln/peer_handler.rs
+++ b/lightning/src/ln/peer_handler.rs
@@ -86,7 +86,7 @@ pub trait SocketDescriptor : cmp::Eq + hash::Hash + Clone {
 pub struct PeerHandleError {
 	/// Used to indicate that we probably can't make any future connections to this peer, implying
 	/// we should go ahead and force-close any channels we have with it.
-	no_connection_possible: bool,
+	pub no_connection_possible: bool,
 }
 impl fmt::Debug for PeerHandleError {
 	fn fmt(&self, formatter: &mut fmt::Formatter) -> Result<(), fmt::Error> {