Stephan T. Lavavej

I observe that this works if I replace `import ;` with `import std;` in `Timer.ixx`. This appears to be a known compiler bug/limitation regarding any mixing of the named Standard...

Slightly reduced: ``` C:\Users\stl\Downloads\Test\Test>type Core.ixx ``` ```cpp export module Core; export import std; ``` ``` C:\Users\stl\Downloads\Test\Test>type Timer.ixx ``` ```cpp module; export module Timer; #ifdef WORKAROUND import std; #else import ;...

The ARM and ARM64 test builds are failing. (With the new CMakePresets, it's easier than ever to build a specific test directory for ARM and ARM64.)

I've pushed a merge with `main` to resolve a trivial adjacent-add conflict with #3925 in ``.

Mixing named modules and classic includes or header units within a single TU is super doomed due to the compiler bug/limitation. Consistent TUs being mixed together during linking is probably...

As foretold, there are merge conflicts with #4113.

I've pushed a merge with `main` to resolve a trivial adjacent-edit conflict with #4143 in ``.

Thanks! This PR was much less scary than I thought it would be. :joy_cat: I pushed a conflict-free merge with `main`, followed by my feedback. Nothing affecting your core algorithm...

Yep, I've verified that #4154 in VS 2022 17.10 Preview 1 has fixed this scenario. I can now successfully build the repro (with 17.10 Preview 4): ``` C:\Users\stl\Downloads\Test>"C:\Program Files\Microsoft Visual...

> It's curious that these failures are x86-only The truncation warnings were x86-only because Google Benchmark apparently always uses 64-bit types for its "range" values. > and are raised from...