madroach
madroach
While preparing a CHANGES entry I found this: >Lwt_main.yield and Lwt_unix.yield are deprecated in favor of the generic Lwt.pause, and Lwt_unix.auto_yield is deprecated in favor of the new Lwt_unix.auto_pause. Currently,...
Yes, resolving paused promises more often may break stuff intending to wait for one whole iteration. But resolving less often? No I don't think so.
added a CHANGES entry
I think this is sensible. There is indeed no relevant difference between yield and pause.
The problem is, I cannot call into Lwt_unix, only core Lwt. Also the documentation says: > In case your callback is just using the CPU for a really long time,...
Hi, thanks for your reply. I chose the wrong wording. The problem is not about pipelining, but only about connection keep-alive. During pipelining, which is currently not supported, it won't...
also mention in the documentation whether terminating null bytes are added.
Please fix the documentation to mention whether terminating null bytes are added or chopped off.
I don't care about the close_notify change so much anymore, but please merge the compatibility changes to support LibreSSL.
@avsm I believe you should review this, since you added support for `MAP_STACK`.