Merge pull request #5882 from TylerMSFT/modules

use the modern way

Author: prmerger-automator[bot]

docs/build/reference/experimental-module.md

@@ -15,9 +15,9 @@ Enables compiler support for Microsoft's experimental form of C++ Standard modul
 
 ## Remarks
 
- This switch was for the time before the new, standardized, way of consuming the C++ Standard Library as modules described in [Import the C++ standard library using modules](../../cpp/tutorial-import-stl-named-module.md) was available. Although you can use this switch to use the older experimental named modules, we recommend that you use the new, standardized, way of consuming the C++ Standard Library as modules described in [Import the C++ standard library using modules](../../cpp/tutorial-import-stl-named-module.md).
+ This switch applies to the time before the new, standardized, way of consuming the C++ Standard Library as modules was available. Although you can use this switch to use the older experimental named modules, we recommend that you use the new, standardized, way of consuming the C++ Standard Library as modules described in [Import the C++ standard library using modules](../../cpp/tutorial-import-stl-named-module.md).
 
-This compiler became available starting in Visual Studio 2015 Update 1. Ensure that **C++ Modules for v143 build tools (x64/x86 - experimental)** in selected the VS Installer. It's available in the **Individual components** tab of the installer. Search for **experimental** to see the option. For more information, see [Install C and C++ support in Visual Studio](../vscpp-step-0-installation.md).
+This compiler switch is available starting in Visual Studio 2015 Update 1. In the VS Installer under the **Individual components** tab, ensure that **C++ Modules for v143 build tools (x64/x86 - experimental)** is selected. You can use the search box with **experimental** to find it. For more information, see [Install C and C++ support in Visual Studio](../vscpp-step-0-installation.md).
 
 | Version  | Status |
 |---|---|
@@ -54,6 +54,7 @@ For more information about how to use and create modules, see [Overview of modul
 
 ## See also
 
+[Import the C++ standard library using modules](../../cpp/tutorial-import-stl-named-module.md)\
 [`/headerUnit` (Use header unit IFC)](headerunit.md)\
 [`/exportHeader` (Create header units)](module-exportheader.md)\
 [`/reference` (Use named module IFC)](module-reference.md)\

docs/build/reference/scandependencies.md

@@ -60,10 +60,8 @@ Consider the following sample code:
 #include <vector>
 
 import other.module;
-import std.core;
-
+import std;
 import "t.h";
-
 import <iostream>;
 
 int main() {}
@@ -83,14 +81,14 @@ The compiler produces a JSON file, *`output.json`*, with content similar to:
         {
             "primary-output": "app.obj",
             "outputs": [
-                "C:\\Users\\username\\source\\repos\\app\\app"
+                "output.json"
             ],
             "requires": [
                 {
                     "logical-name": "other.module"
                 },
                 {
-                    "logical-name": "std.core"
+                    "logical-name": "std"
                 },
                 {
                     "logical-name": "t.h",
@@ -134,6 +132,7 @@ To report module and header unit dependencies, you must also set the **Configura
 
 ## See also
 
+[Import the C++ standard library using modules](../../cpp/tutorial-import-stl-named-module.md)\
 [MSVC compiler options](compiler-options.md)\
 [MSVC compiler command-line syntax](compiler-command-line-syntax.md)\
 [`/sourceDependencies:directives`](sourcedependencies-directives.md)\

docs/build/reference/sourcedependencies-directives.md

@@ -59,10 +59,8 @@ Given the following sample code:
 #include <vector>
 
 import m;
-import std.core;
-
+import std;
 import <utility>;
-
 import "t.h";
 
 int main() {}
@@ -78,15 +76,16 @@ produces a JSON file *`output.json`* similar to:
 {
    "Version":"1.1",
    "Data":{
-      "Source":"C:\\a\\b\\main.cpp",
+      "Source":"C:\\test\\main.cpp",
       "ProvidedModule":"",
       "ImportedModules":[
          "m",
-         "std.core"
+         "std"
       ],
       "ImportedHeaderUnits":[
          "C:\\...\\utility",
-         "C:\\a\\b\\t.h"
+         "C:\\...\\vector",
+         "C:\\test\\t.h"
       ]
    }
 }
@@ -104,6 +103,7 @@ You normally shouldn't set this option yourself in the Visual Studio development
 
 ## See also
 
+[Import the C++ standard library using modules](../../cpp/tutorial-import-stl-named-module.md)\
 [`/translateInclude`](translateinclude.md)\
 [C++ header-units.json reference](header-unit-json-reference.md)\
 [MSVC compiler options](compiler-options.md)\

docs/cpp/import-export-module.md

@@ -7,7 +7,7 @@ description: Use import and export declarations to access and to publish types a
 ---
 # `module`, `import`, `export`
 
-The **`module`**, **`import`**, and **`export`** declarations are available in C++20 and require the compiler switch [`/std:c++20`](../build/reference/std-specify-language-standard-version.md) or later (such as **`/std:c++latest`**). For more information, see [Overview of modules in C++](modules-cpp.md).
+The **`module`**, **`import`**, and **`export`** declarations are available in C++20 and require the compiler switch [`/std:c++20`](../build/reference/std-specify-language-standard-version.md) or later. For more information, see [Overview of modules in C++](modules-cpp.md).
 
 ## `module`
 
@@ -43,8 +43,6 @@ namespace ModuleA_NS
 Non-exported names aren't visible to code that imports the module:
 
 ```cpp
-//MyProgram.cpp
-
 import ModuleA;
 
 int main() {
@@ -64,9 +62,8 @@ Use an **`import`** declaration to make a module's names visible in your program
 module ModuleA;
 
 #include "custom-lib.h"
-import std.core;
-import std.regex;
-import ModuleB;
+import std;
+import myModule;
 
 // begin declarations here:
 template <class T>
@@ -114,4 +111,5 @@ import // Always an identifier, never a keyword
 
 ## See Also
 
-[Overview of modules in C++](modules-cpp.md)
+[Overview of modules in C++](modules-cpp.md)\
+[Import the C++ standard library using modules](tutorial-import-stl-named-module.md)

docs/cpp/modules-cpp.md

@@ -1,7 +1,7 @@
 ---
 title: "Overview of modules in C++"
 description: Modules in C++20 provide a modern alternative to header files.
-ms.date: 02/11/2025
+ms.date: 04/17/2025
 helpviewer_keywords: ["modules [C++]", "modules [C++], overview"]
 ---
 # Overview of modules in C++
@@ -48,8 +48,8 @@ The file *`MyProgram.cpp`* uses **`import`** to access the name exported by `Exa
 
 ```cpp
 // MyProgram.cpp
+import std;
 import Example;
-import std.core;
 
 using namespace std;
 
@@ -156,7 +156,7 @@ You can include header files in a module source file by putting an `#include` di
 #include "customlib.h"
 #include "anotherlib.h"
 
-import std.core;
+import std;
 import MyModuleB;
 
 //... rest of file
@@ -166,9 +166,10 @@ You can use a traditional header file to control which modules are imported:
 
 ```cpp
 // MyProgram.h
-import std.core;
-#ifdef DEBUG_LOGGING
-import std.filesystem;
+#ifdef C_RUNTIME_GLOBALS
+import std.compat;
+#else
+import std;
 #endif
 ```
 
@@ -183,6 +184,7 @@ import "myheader.h";
 
 ## See also
 
+[Import the C++ standard library using modules](tutorial-import-stl-named-module.md)\
 [`module`, `import`, `export`](import-export-module.md)\
 [Named modules tutorial](tutorial-named-modules-cpp.md)\
 [Compare header units, modules, and precompiled headers](../build/compare-inclusion-methods.md)