snailspeed3

Really excellent writeup. I think this will be relatively low priority as the game itself makes no use of C++ exceptions--the vast majority of the unwind tables were accidentally generated...

Yep. Ideally let's integrate this with diff.py. If we generate DWARF info from our sources we could also point to the exact file/line number where the issue is--perhaps automatically putting...

Partially solved with diff.py. I would like to take this in the direction outlined by #42.

We should probably specify the clang-equivalent of `-MT` (on clang-cl) when on Windows. It is odd that if you run `SET CXX=clang` before `cargo build` on Windows, the `-Ctarget-feature=+crt-static` RUSTFLAG...

> We should get a product decision: if this message is annoying and we want to get rid of it, let's think on a different approach rather than this sentinel...

> Fatal error: expected: No such file or directory This would indicate an incompatible C++ compiler version, given the [`` header was introduced in C++23](https://en.cppreference.com/w/cpp/utility/expected).

That failing you could configure with `cmake .. -DCMAKE_BUILD_TYPE=Release -DCMAKE_CXX_FLAGS="-DRSL_STACKTRACE_UNSUPPORTED=1"`, though that would be a reduction of functionality and far less preferable to what Joshua suggested.

With the above changes, I was able to build with GCC 14.1.0 on Ubuntu 22.04.4 LTS. Since I didn't configure stacktrace support when I built the compiler, I configured with...

Thanks for the swift reply. > test if the same issue occurs with corrosion on the master branch I apologize for not mentioning I had tried this locally. Here's a...

> I'm guessing that this may actually be the issue. It really doesn't seem like it? I pushed a run with it added back, and on lld, which completes our...