From 0ebf70d6a24c97f8df9620d11cc29aae798cea72 Mon Sep 17 00:00:00 2001 From: Matt Corallo Date: Fri, 28 Feb 2020 14:28:13 -0500 Subject: [PATCH] Drop stale doc comment + TODO describing MessageSendEvents --- lightning/src/util/events.rs | 7 ------- 1 file changed, 7 deletions(-) diff --git a/lightning/src/util/events.rs b/lightning/src/util/events.rs index a41b7a3bb..d165f200a 100644 --- a/lightning/src/util/events.rs +++ b/lightning/src/util/events.rs @@ -4,13 +4,6 @@ //! Because we don't have a built-in runtime, it's up to the client to call events at a time in the //! future, as well as generate and broadcast funding transactions handle payment preimages and a //! few other things. -//! -//! Note that many events are handled for you by PeerHandler, so in the common design of having a -//! PeerManager which marshalls messages to ChannelManager and Router you only need to call -//! process_events on the PeerHandler and then get_and_clear_pending_events and handle the events -//! that bubble up to the surface. If, however, you do not have a PeerHandler managing a -//! ChannelManager you need to handle all of the events which may be generated. -//TODO: We need better separation of event types ^ use ln::msgs; use ln::channelmanager::{PaymentPreimage, PaymentHash}; -- 2.39.5