Anil Madhavapeddy

How about leaving the default to io_uring, but making fixed buffers optional via an environment variable instead of ripping them out? It would be nice to leave that functionality in...

@UnixJunkie would you mind taking a look at the issues above please, or closing this?

I'm trying to reproduce the crash but have only gotten it once on the bigger program from which I extracted this testcase ``` ThreadSanitizer:DEADLYSIGNAL ==800191==ERROR: ThreadSanitizer: SEGV on unknown address...

+1 to this request from me as well! I've personally been moving my code over to [Tangled on Bluesky](https://anil.recoil.org/notes/disentangling-git-with-bluesky) and would find it very useful to have multiple mirrors of...

I'm personally ok waiting till opam 3 for this rather than forcing intermediate hacks. Although, I guess that any x- field could just be rewritten automatically into the "proper" field...

The configure-time parameter seems safe here, but bear in mind that OS packagers are unlikely to do the right thing by default, so it would be great to ensure that...

@vog have you had a chance to look at the above? Happy to help with any questions you have about opam, if any, but you need to make the decisions...

> Seems like socket options could be useful on non-Unix systems too. We could define the type in Eio.Net as an extensible variant and put the common ones there, adding...

I've pushed a rebase with all the suggestions here. There are loads of Linux and Windows specific ones to add, but I wanted to check if this is version is...

I've added a bunch of Linux specific calls now (skipping multicast for now, and some of the more exotic fast connect and tcp_info ones), and also dropped SO_ACCEPTCON as it's...