Thank you for the compliment. But I was merely channeling Jonathan Worthington... :-)
> On 30 Dec 2020, at 14:43, Gianni Ceccarelli <dak...@thenautilus.net> wrote: > > Liz is, as usual, correct: there's no reason to wait until our write > buffers are flushed (``await $conn.print``) before ``react``ing to > what's in our *read* buffers. > > In https://github.com/dakkar/raku-socket-test-from-demanuel I've > removed all ``await`` but one (the ``await .connect``), and the > program is much more reliable. I have seen it hang once, though, > so I feel there's still some weirdness going on with buffers > *somewhere*. > > David: please look at my version of your code, I really think it's > clearer and simpler to work with, without the explicit ``.tap`` and > ``.then`` (ok, I have a few ``.then``, but they're for debugging, they > don't affect the actual working of the program!) > > -- > Dakkar - <Mobilis in mobile> > GPG public key fingerprint = A071 E618 DD2C 5901 9574 > 6FE2 40EA 9883 7519 3F88 > key id = 0x75193F88 >
