wil

Anything related to WinUI is a bad joke. Have fun following the discussions and amount of bugs, https://github.com/microsoft/microsoft-ui-xaml That C++ support that WinUI team marketing keeps talking about relies on a framework that is no longer being developed. > The reason the issues page only lets you create a bug report is because cppwinrt is in maintenance mode and no longer receiving new feature work. cppwinrt serves an important and specific role, but further feature development risks destabilizing the project. Additional helpers are regularly contributed to complimentary projects such as https://github.com/microsoft/wil/. From https://github.com/microsoft/cppwinrt/issues/1289#issuecomme...

Great analysis, but the solution is so simple: RAII. And this is offered as `unique_process_handle`[1] in the Windows Implementation Library (WIL)[2]. This is a fantastic addition to the Windows developer's toolkit, which everyone should be using from the outset. The Windows C API is unnecessarily verbose (although this can be said of any OS, Windows' is particularly bad), and simple mistakes can and will happen. Let RAII help you, let the mighty close-scope token `} ` be your best friend. [1]: https://github.com/microsoft/wil/blob/1f20cd086e07b9be54e70d... [2]: https://github.com/microsoft/wil

In that case, make yourself a favour and use WIL, aka Windows Implementation Library. https://github.com/microsoft/wil

> If it's not Cygwin, then what is it? Looking at the source code[1], it appears to be analogous to MinGW in the MinGW:GNU/Linux:Windows relationship, but replace with MinC:BSD:Windows. In other words, a minimal user-mode layer that presents BSD headers (and therefore BSD symbols, macros, and types), libraries, and core utils to end-users, thus abstracting over MSVC†. EDIT: replace 'MinGW' with 'Cygwin' above. So it is Cygwin. I'd say calling it a 'kernel' is quite a stretch—there is not much that runs in kernel-mode, and everything runs atop the NT kernel which does the actual 'kernel'y stuff. [1]: https://github.com/dboland/minc †: Until one wants to use very recent and very nice Microsoft libraries[2][3], and these fail spectacularly because MinGW doesn't know about nice MSVC-specific stuff like SAL annotations[4]. [2]: https://github.