Skip to content

Commit 264b7e0

Browse files
authored
Remove 'product' references
1 parent 9daca00 commit 264b7e0

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

proposals/0403-swiftpm-mixed-language-targets.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -302,20 +302,20 @@ build nodes for the its `SwiftTargetBuildDescription` and
302302

303303
##### Module Maps
304304

305-
The product module map’s purpose is to define the public API of the mixed
305+
The client-facing module map’s purpose is to define the public API of the mixed
306306
language module. It has two parts, a primary module declaration and a secondary
307307
submodule declaration. The former of which exposes the public C language
308308
headers and the latter of which exposes the generated interop header.
309309

310-
There are two cases when creating the product module map:
310+
There are two cases when creating the client-facing module map:
311311
- If a custom module map exists in the target, its contents are copied and
312312
extended to modularize the generated interop header. These contents are
313313
written to the build directory as `extended-custom-module.modulemap`.
314314
Since the public header directory and build directory are passed as import
315315
paths to the build invocations, a different name is needed for this module
316316
map as the `-import-underlying-module` should only be able to find one
317317
`module.modulemap` file from the given import paths.
318-
- Else, the product module map’s contents will be generated via the same
318+
- Else, the module map’s contents will be generated via the same
319319
generation rules established in [SE-0038] with an added step to generate the
320320
`.Swift` submodule. This file is called `module.modulemap` and lives in the
321321
build directory.

0 commit comments

Comments
 (0)