From ed335e68f44a00ea77b83f356f5fa6a055eae989 Mon Sep 17 00:00:00 2001
From: Henry de Valence <hdevalence@hdevalence.ca>
Date: Tue, 15 Oct 2019 15:01:07 -0700
Subject: [PATCH] Remove outdated comment

Now that the `PeerConnector` handles both incoming and outgoing
handshakes, determining the next peer address is definitely out of scope
-- it takes a pre-existing tcp connection.
---
 zebra-network/src/peer/connector.rs | 2 --
 1 file changed, 2 deletions(-)

diff --git a/zebra-network/src/peer/connector.rs b/zebra-network/src/peer/connector.rs
index 70668c0a..c3a44de7 100644
--- a/zebra-network/src/peer/connector.rs
+++ b/zebra-network/src/peer/connector.rs
@@ -69,8 +69,6 @@ where
     type Future = Pin<Box<dyn Future<Output = Result<Self::Response, Self::Error>>>>;
 
     fn poll_ready(&mut self, _cx: &mut Context<'_>) -> Poll<Result<(), Self::Error>> {
-        // XXX when this asks a second service for
-        // an address to connect to, it should call inner.ready
         Poll::Ready(Ok(()))
     }