Quinton Miller

`MODIFIER_KEY_STR`'s _initializer_ is a `MacroIf` that only gets expanded in the main phase, rather than a `StringLiteral`. The two are not quite the same.

Why `#private?` instead of `#visibility`?

Apparently there are also "I/O rings" on Windows since 21H2: https://learn.microsoft.com/en-us/windows/win32/api/ioringapi/ They are apparently very similar to `io_uring`: https://windows-internals.com/ioring-vs-io_uring-a-comparison-of-windows-and-linux-implementations/

The Win32 equivalent is [`WriteFileGather`](https://learn.microsoft.com/en-us/windows/win32/api/fileapi/nf-fileapi-writefilegather), which requires page-aligned buffers...?

A while ago I managed to get it working (Crystal could even build itself on Termux), but I forgot the exact list of dependencies: https://forum.crystal-lang.org/t/running-crystal-on-termux/3880

Heads up: Crystal's master branch now has [support for AArch64 Android](https://github.com/crystal-lang/crystal/pull/13065) (via `--target=aarch64-linux-android`), but not LLVM 15+ nor API levels 24 - 27 yet

Would this fit better in crystal-lang/perf-tools, or does it touch so many internals that a shard implementation is impossible?

> what if it were in a location that is guaranteed to exist? I.e., what if Crystal shipped the certificates in the `lib` directory, then you can be certain that...

So it appears the last option is far easier than I anticipated. Here is a fully working example, using [cURL's source code](https://github.com/curl/curl/blob/2f17a9b654121dd1ecf4fc043c6d08a9da3522db/lib/vtls/openssl.c#L3021-L3156) as a reference: ```crystal require "openssl" # lib_crypto.cr...

To be clear, there are a few different toolchains possible on Windows: | Toolchain | Compiler | Triple | Flags | Additional runtimes | |-|-|-|-|-| | Microsoft Visual C++ |...