Russel Winder

The line: ``` let socket = futures::ready!(future.poll(cx))?; ``` is giving the error: ``` error[E0599]: no method named `poll` found for struct `std::pin::Pin` in the current scope ``` UPDATE: Seemingly solved...

I think I have been distracted by the comments about calling close: the comments are actually C and not Rust focused. As long as close automatically gets called at end...

As at 2020-05-08, the line: ```rust for connection in server.incoming() { ``` given the error: ``` error[E0277]: `arcamclient::socket_support::Incoming: std::future::Future` is not satisfied ```

@sdroege Thanks. I was looking at the wrong incoming() documentation for ideas. I am wondering if it might be worth creating a temporary Git repository for this as a work...

It appears that: ```rust for socket_connection in server.incoming().next().await { ``` blocks permanently even when a connection request arrives. :-( Update: Actually, it is exactly the opposite, the loop terminates immediately....

I am switching to using this Git repository rather than the version I had in my repository. I'll send in issues as (if) I come across them. This requires using...

OK. I am stuck with Dub and SCons for build since Meson cannot build Unit-Threaded stuff because there is no unitary build. (I just do a small hack for the...

@ximion I had sort of assumed that an installation (at least on Linux) should always install both static and dynamic libraries. This is what I have done for DInotify and...

Sounds like I should update the DInotify and Unit-Threaded builds then, so as to only produce the shared libraries.

I got pointed at this issue by @killercup on https://users.rust-lang.org/t/cargo-and-installation-of-ancilliary-files/15974 My specific problem is installing a GNOME application. So not a CLI application per se, but very similar. Whilst many...