You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/build/reference/experimental-module.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,13 +15,13 @@ Enables experimental compiler support for modules, as specified by the draft C++
15
15
16
16
## Remarks
17
17
18
-
You can enable experimental modules support by use of the **/experimental:module** compiler option along with the [/std:c++latest](std-specify-language-standard-version.md) option. You can use **/experimental:module-** to disable module support explicitly.
18
+
You can enable experimental modules support by use of the **`/experimental:module`** compiler option along with the [/std:c++latest](std-specify-language-standard-version.md) option. You can use **`/experimental:module-`** to disable module support explicitly.
19
19
20
-
This option is available starting in Visual Studio 2015 Update 1. As of Visual Studio 2019 version 16.2, Draft C++20 Standard modules are not fully implemented in the Microsoft C++ compiler. You can use the modules feature to create single-partition modules and to import the Standard Library modules provided by Microsoft. A module and the code that consumes it must be compiled with the same compiler options.
20
+
This option is available starting in Visual Studio 2015 Update 1. As of Visual Studio 2019 version 16.2, Draft C++20 Standard modules aren't fully implemented in the Microsoft C++ compiler. You can use the modules feature to create single-partition modules and to import the Standard Library modules provided by Microsoft. A module and the code that consumes it must be compiled with the same compiler options.
21
21
22
22
For more information on modules and how to use and create them, see [Overview of modules in C++](../../cpp/modules-cpp.md).
23
23
24
-
Here's an example of the compiler command-line options used to create an export module from source file *ModuleName.ixx*:
24
+
Here's an example of the compiler command-line options used to create an export module from source file *`ModuleName.ixx`*:
# `/sourceDependencies:directives` (Report source-level dependencies and use an allow-list)
8
+
# `/sourceDependencies:directives` (Report source-level dependencies and use an allowlist)
9
9
10
10
This command-line switch generates a JSON file that details the source-level dependencies consumed during compilation. It also looks for a `header-units.json` file that specifies which header files can be converted to header units.
11
11
@@ -23,7 +23,7 @@ This command-line option is similar to [`/sourceDependencies`](sourcedependencie
23
23
## Arguments
24
24
25
25
*`-`*\
26
-
If the single dash is provided then the compiler will emit the source dependencies JSON to `stdout` or where the compiler output is redirected to.
26
+
If the single dash is provided, then the compiler will emit the source dependencies JSON to `stdout` or where the compiler output is redirected to.
27
27
28
28
*`filename`*\
29
29
The compiler writes the source dependency output to the specified filename, which may include a relative or absolute path.\
@@ -43,7 +43,7 @@ All file paths appear as absolute paths in the output.
43
43
44
44
This switch is used in combination with [`/translateInclude`](translateinclude.md).
45
45
46
-
`header-units.json` is used with the build system's **Scan Sources for Module Dependencies** to determine which header files can be compiled into a header unit. When this switch is specified, header files encountered in the scanned source files, that are also listed in `header-units.json`, are considered eligible to be compiled into header units. Files not in the list are instead treated as a normal `#include`.
46
+
`header-units.json` is used with the build system's **Scan Sources for Module Dependencies** to determine which header files can be compiled into a header unit. When this switch is specified, header files found in the scanned source files, that are also listed in `header-units.json`, are considered eligible to be compiled into header units. Files not in the list are instead treated as a normal `#include`.
47
47
48
48
The compiler looks for `header-units.json` where the header being loaded is located. For more information about the format of this file, see [C++ header-units.json reference](..\header-unit-json-reference.md)
0 commit comments