João Costa

Personally, I would also prefer a `.bat`/`.ps1` instead of a dockerfile. If I need to run that on a dockerfile on windows, I might as well run it using WSL.

I get the same error on Mac OS X (x86), so it can't be a Windows thing (I did get one run that didn't fail, though). ``` % scala-cli test...

> Similarry usage of Future.successful(2) seems to work correctly. For reference `Future(assertEquals(1 + 1, 2))` also works (even without the `successful`), that's why I used `map` on the example.

Thanks for looking into it, I'll try the workarounds. One thing that I'm curious: When you say: > the OpCode 4 is responsible for sending an event from Native worker...

Another update. I tried a modified version of scala native where I renamed main to `SDL_main` and the application launches for a few moments, but then dies. ~The crashes are...

> I don't know how to handle the runtime behavior, yet. Probably we might be forced to debug it by stepping the dissembled code in WinDBg or Visual Studio. Just...

> I am a provincial, but having "LTO=thin" with "debug" looks strange Yes, that was an oversight on my part, I already changed it on that PR. I'll try to...

Looks like that worked as well: https://github.com/JD557/minart/actions/runs/4218614159/jobs/7323250192 (Now I'm wondering if the problem is actually fixed or if it is going to appear again in the future once I update...

I believe the problem happened in Ubuntu 22.04.02, whose default Clang version seems to be 14 Locally I was using with Windows 11 and Clang 12 with no problems (unfortunately,...

Looking at https://github.com/scala-native/scala-native/blob/f4b9078c6c96dade366518f037d8f47048d2a4f3/util/src/main/scala/scala/scalanative/io/VirtualDirectory.scala, I see quite a bit of `try {...} finally {file.close()}` in there, which might be swallowing exceptions. Maybe it would be a good idea to replace those...