[pippocao]

The module entry is a binary of its own now. A translation unit may not import and include the same library (MSVC refuses it with C2300), so it cannot be compiled into BqLogUnitTest next to the include entry; the test runners start it right after BqLogUnitTest, which is what keeps it compiled and run on every platform that can build modules.

Also in here:

• the library builds once as an object library that both test binaries link;
• the module target's file set is PUBLIC (CMake refuses an import from outside otherwise) and the importing target sets CXX_SCAN_FOR_MODULES, instead of a project wide CMP0155;
• the global module fragment pre-includes bq's assert wrapper: <assert.h> has no include guard, so the purview includes it again and MSVC reports C5244, which /W4 /WX turns into an error;
• type_tools names the destructor through the nested template's own parameter, which MSVC cannot do through the enclosing T inside a module;
• test_fast_log uses strtol instead of the deprecated sscanf, which was failing the MSVC test build on its own;
• the module test has its own main() and removes the log file of an earlier run, which it otherwise appended to and counted twice.

Verified locally, both binaries, full suite green: MSVC (VS 18 Insiders, /W4 /WX) and MinGW GCC 15.2. The module entry reports test_module 9/9 and is idempotent.

[tencent-adm]

Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

pippocao seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}