P1767 Packaging C++ Modules

[wg21bot]

P1767R0 Packaging C++ Modules (Richard Smith)

[brycelelbach]

Cologne 2019-07 SG15 Minutes

P1767R0 Packaging Modules

Champion: Richard Smith

Minute Taker: Conor Hoekstra

Start Overview: 07-19 11:25

Start Review: 11:42

Start Polling: 11:57

POLL: Adopt P1767R0 as the basis of our strategy for addressing build system interchange (modulo bikeshedding) in the C++ Modules Ecosystem Technical Report.

Strongly For	Weakly For	Neutral	Weakly Against	Strongly Against
7	6	4	0	0

Attendance: 18

That has unanimous consensus.

End: 12:11

CONSENSUS: P1767R0 is the basis of our strategy for addressing build system interchange (modulo bikeshedding) in the C++ Modules Ecosystem Technical Report.

Referral to SG16 for path encoding.

[brycelelbach]

Cologne 2019-07 SG15 Minutes

P1767R0 Packaging Modules

Champion: Richard Smith

Minute Taker: Mark Zeren

Start Review: 07-19 15:59

Add example of module aliasing (on the command line).

Start Polling: 16:35

POLL: SG15 should prioritize solving the module name collision problem.

Strongly For	Weakly For	Neutral	Weakly Against	Strongly Against
0	9	8	1	0

Attendance: 19

This has weak consensus.

POLL: SG15 should prioritize solutions for dealing with source-level module name collisions (e.g. module aliasing/renaming/remapping).

Strongly For	Weakly For	Neutral	Weakly Against	Strongly Against
4	8	1	3	0

Attendance: 19

This has consensus.

POLL: SG15 should prioritize solutions for avoiding module name collisions.

Strongly For	Weakly For	Neutral	Weakly Against	Strongly Against
1	6	9	1	0

Attendance: 19

This has weak consensus.

POLL: SG15 should prioritize solutions for dealing with link-level module name collisions.

Strongly For	Weakly For	Neutral	Weakly Against	Strongly Against
3	8	2	4	0

Attendance: 19

That has weak consensus.

A: It's a very hard problem. We can't prioritize everything.

Typos in paper:

• configureA
• fixiz

End: 16:46

CONSENSUS: Bring a revision of P1767R0, with the guidance below, to SG15 for further review.

• Focus exploration of module name collision solutions on dealing with source-level module name collisions (e.g. module aliasing/renaming/remapping).