P1881 Epochs: a backward-compatible language evolution mechanism

[wg21bot]

P1881R0 Epochs: a backward-compatible language evolution mechanism (Vittorio Romeo)

[theres-waldo]

EWG-I in Belfast

Do we want to solve the problem of being able to clean up C++ and improve defaults, while maintaining backwards compatibility?

SF	F	N	A	SA
22	2	2	0	0

Do we want to see P1881 again with a more refined version of the mechanism and a small set of polished features as an example?

SF	F	N	A	SA
15	3	4	1	1

Do we want user-defined rulesets for a mechanims like the proposed one?

SF	F	N	A	SA
2	0	2	5	15

Should new non-breaking features always be confined to the latest epoch?

SF	F	N	A	SA
4	4	4	5	4

[brycelelbach]

Belfast 2019-11 Tooling Minutes

P1881R0 Epochs

Chair: Bryce Adelstein Lelbach

Champion: Vittorio Romeo

Minute Taker: Tom Honermann

Start Review: 11-08 11:49

End: 12:10

CONSENSUS: Bring a revision of P1881R0 (Epochs) to the Tooling Study Group.

[wg21bot]

P1881R1 Epochs: a backward-compatible language evolution mechanism (Vittorio Romeo)

[theres-waldo]

CONSENSUS: Bring a revision of P1881R0 (Epochs) to the Tooling Study Group.

Adding SG15 label based on this.

[erichkeane]

EWG-I in Prague

Do we believe the problem that D/P1881 attempts to solve is worth solving?

SF	F	N	A	SA
1	17	4	2	0

Given the time constraints of the committee, should we spend additional committee effort on D/P1881?

SF	F	N	A	SA
0	4	7	7	7

Are copy paste/textual inclusion limitations a problem that needs to be solved before we see epochs again?

SF	F	N	A	SA
6	4	8	3	1

Does D/P1881 need to solve the template problems before we look at it again?

SF	F	N	A	SA
20	1	1	0	0