Anton Bachin

@gabelevi, on Windows, only sockets can be non-blocking (in the Unix sense). Among other problems, you may have a fd that Lwt thinks is non-blocking, but is actually blocking. What...

@bryphe I don't think that the `O_NONBLOCK` is the problem: 1. `Lwt_io.with_file` eventually does call `Lwt_unix.openfile` with `O_NONBLOCK`, and that flag is indeed meaningless (on any system for a regular...

You may be able to get some information by attaching a finalizer to the `Lwt_io` channel (i.e., the argument `Lwt_io.with_file` passes to your function) using `Gc.finalise`, and triggering a garbage...

The tests use a shortcut here, and shouldn't be taken to imply any "formal" statements about how polymorphic equality works on promises outside the test suite in this repo. In...

I looked in the Lwt source code, and a bit in OCaml, and I don't immediately see the problem. Since I don't have easy access to a MinGW install to...

> I can investigate further by looking at the lwt codebase. That would probably be the most helpful. Thanks if you do. In addition to the code I linked above,...

Excellent investigation, thank you. It looks like the select engine and the code that interacts with it in `Lwt_unix` would need non-trivial modification to fix this the "right way." There...

@essdotteedot You may benefit by replacing `lwt.unix` by [`uwt`](https://github.com/fdopen/uwt), which is based on libuv and probably has most issues like this one resolved. I'm under the impression that uwt works...

(...and we would like to replace `lwt.unix` by `uwt` in this repo, #328).

Should be more feasible now with https://github.com/aantron/luv.