Stephan T. Lavavej

Mixing modules with classic includes is a known bug/limitation that the compiler team is working on. This should also not be expected to work at all at this time. (It's...

Does this still repro with VS 2022 17.10 Preview 7 or later? I improved the STL so that include-before-import (*but not the other order*) works, with #4154 in VS 2022...

> crtdbg.h is not a STL header, so it should not be affected by the current limitation of mixing import std and includes. Unfortunately it is, because it's dragging in...

I've pushed a conflict-free merge with main to pick up the 17.12p2 / Clang 18 toolset update. (This isn't usually critical, but it was a big reformatting PR.) No clang-format...

Thanks! :heart_eyes_cat: I pushed a conflict-free merge with `main` followed by several refactorings, shrinking the diff from +181 -2 to +115 -10. Originally, this PR looked like it was adding...

I'm mirroring this to the MSVC-internal repo - please notify me if any further changes are pushed.

Thanks for figuring out the surprisingly complicated logic needed to make these functions fast! :rocket: :heart_eyes_cat: :green_heart:

`extern "C++"` will also attach to the global module. @cdacamar, is this a Stuff Just Works scenario? I can't control your implicit declarations emitted by the compiler.

This also affects `rttidata.h`'s forward declaration of `type_info`. Because I'm lazy, I'd like the compiler to take care of its own implicit declarations (i.e. creating special exemptions from the "must...

At this point I haven't yet validated Clang with `import std;`. My preference would be for them to similarly special-case their pre-declarations, but if I must modify `std.ixx` then I...