About Windows named pipe APIs missing

[jinzhongjia]

Named pipe is a commonly used solution for inter-process communication. For example, neovim uses named pipes by default on Windows, and unixsocket is used by default on Linux for RPC calls.According to Microsoft's document, windows provides some useful encapsulation functions.

Existing APIs

I have read through the Windows API in the standard library and found that there are some named pipe APIs.
Like: CreateNamedPipeW, CreatePipe.
But I didn't find more apis about namedpipe, maybe we need to improve this part?

For examples:

• CallNamedPipeW
• ConnectNamedPipe
• DisconnectNamedPipe
• GetNamedPipeClientComputerNameW
• GetNamedPipeHandleStateW
• GetNamedPipeInfo
• ImpersonateNamedPipeClient
• PeekNamedPipe
• SetNamedPipeHandleState
• TransactNamedPipe
• WaitNamedPipeW

[squeek502]

Zig is not intending on providing Windows API bindings that it does not use internally: #4426

If you'd like to use these functions in your own project you can write the relevant bindings directly in your project, or use zigwin32 if you want something comprehensive.

See also:

• Prefer depending on NtDll rather than kernel32 or other higher level DLLs #1840
• Windows: Prefer ntdll named pipe APIs over kernel32 #19037