[gnunet-scheme] 04/08: dht/client: Explain why the connection:interrupted code is correct.

[gnunet]

This is an automated email from the git hooks/post-receive script.

maxime-devos pushed a commit to branch master
in repository gnunet-scheme.

commit f95e0024a025f816a04e8f243b10c2564c42c1e5
Author: Maxime Devos <maximedevos@telenet.be>
AuthorDate: Thu Feb 3 13:08:54 2022 +0000

    dht/client: Explain why the connection:interrupted code is correct.
    
    * gnu/gnunet/dht/client.scm
      (reconnect)[error-handler]<connection:interrupted>: Remove TODO,
      explain why nothing should be done here and add a reference to the
      test suite.
---
 gnu/gnunet/dht/client.scm | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/gnu/gnunet/dht/client.scm b/gnu/gnunet/dht/client.scm
index 96ddece..ddb1c5d 100644
--- a/gnu/gnunet/dht/client.scm
+++ b/gnu/gnunet/dht/client.scm
@@ -791,8 +791,10 @@ code automatically tries to reconnect, so @var{connected} 
can be called after
           ;; Tell the event loop that it is time to restart,
           ;; unless it is already stopping.
           (maybe-send-control-message!* terminal-condition 'reconnect!))
-         ;; TODO: is this cargo-copying from (gnu gnunet nse client)
-         ;; correct?
+         ;; 'control' closed the queue and will exit, nothing to do here!
+         ;;
+         ;; Tested by "(DHT) close, not connected --> all fibers stop,
+         ;; no callbacks called" in tests/distributed-hash-table.scm.
          ((connection:interrupted)
           (values))
          (else

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.