Quinton Miller

Right before the `yield` in your `test` method: ```crystal def test(&) match = /o/.match!("foo") $~ = $~ yield match end ```

> The major issue is probably that these proc literals look like _normal_ code (except the uncommon type restrictions) but are actually intended for macro code. Constants that are used...

The inlining changes the semantics of a program (see https://github.com/crystal-lang/crystal/pull/16303#issuecomment-3480951326 and https://github.com/crystal-lang/crystal-book/issues/856), so disabling it is not an option.

It could be Windows' own anti-virus: https://stackoverflow.com/questions/1753209/deletefile-fails-on-recently-closed-file

It looks like LLVM 20 supports a new "standard" expection handling proposal while still enabling the "legacy" one by default: https://github.com/llvm/llvm-project/blob/release/20.x/llvm/docs/ReleaseNotes.md#changes-to-the-webassembly-backend

For the record, it looks like disabling FastISel or enabling GlobalISel doesn't actually help

Does #16023 unblock this?

Stack overflow detection relies on the current thread's stack bounds. On Linux this is obtained using `LibC.pthread_getattr_np` and `LibC.pthread_attr_getstack`: https://github.com/crystal-lang/crystal/blob/d58ede5bacba23fbefed9040066aacec44ca953d/src/crystal/system/unix/pthread.cr#L118-L123 However, on musl-libc the internal stack size is always [hardcoded](https://git.musl-libc.org/cgit/musl/tree/src/thread/pthread_create.c?id=dd1e63c3638d5f9afb857fccf6ce1415ca5f1b8b#n267)...

`libtinfo5` was originally needed for the LLVM 16.0.0 binaries, and is unnecessary for 16.0.3, but it appears all the LLVM 18 packages also have this problem; in short, [anything built...

The VM I have right now says: ``` $ uname -a SunOS omnios2 5.11 omnios-r151048-4a265be889 i86pc i386 i86pc ```