asynchronous

It seems to me that if you have a wrapper function
https://github.com/libuv/libuv/blob/a39009a5a9252a566ca0704d02df8dabc4ce328f/test/runner-unix.c#L45
for close, then in this places you can use it.
https://github.com/libuv/libuv/blob/a39009a5a9252a566ca0704d02df8dabc4ce328f/test/runner-unix.c#L336
https://github.com/libuv/libuv/blob/a39009a5a9252a566ca0704d02df8dabc4ce328f/test/runner-unix.c#

Right now, whenever Zenmap crashes, it gives the user a stack trace and asks the user to send it to the Nmap dev list. So we get a flood of emails (most of which aren't even allowed through moderation) which often contain just a stack trace with no subject line or any explanatory text in the message body. Lots of these are for well known issues in older versions of Zenmap. So it's not very usef

Currently the reference guide #content div has max-width: 62.5em set.
This is a bit on the low end for large screens in landscape mode, and could instead be set to eg. 60%.
Beyond that the rendering is starting to feel too large for paragraphs, but at 60% most large codeblocks read far better.

For phones, detecting portrait orientation and setting the max-width to 100% would also be a

Document the newly introduced data types from zio.concurrent:

• ConcurrentMap
• ConcurrentSet
• CountdownLatch
• CyclicBarrier

Replace concrete Bastion Executor with Agnostik.
So everyone can use whatever they want as guarantee.