Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
P1881 Epochs: a backward-compatible language evolution mechanism #631
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?
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?