New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
P1881 Epochs: a backward-compatible language evolution mechanism #631
Comments
Do we want to solve the problem of being able to clean up C++ and improve defaults, while maintaining backwards compatibility?
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?
Do we want user-defined rulesets for a mechanims like the proposed one?
Should new non-breaking features always be confined to the latest epoch?
|
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. |
P1881R1 Epochs: a backward-compatible language evolution mechanism (Vittorio Romeo) |
Adding SG15 label based on this. |
Do we believe the problem that D/P1881 attempts to solve is worth solving?
Given the time constraints of the committee, should we spend additional committee effort on D/P1881?
Are copy paste/textual inclusion limitations a problem that needs to be solved before we see epochs again?
Does D/P1881 need to solve the template problems before we look at it again?
|
P1881R0 Epochs: a backward-compatible language evolution mechanism (Vittorio Romeo)
The text was updated successfully, but these errors were encountered: