You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The standard library specification is filling up with concepts, especially "exposition only" concepts, and Cpp17Requirements. It is often necessary to locate the definition of these concepts to understand the clause you are reading, and there is no easy collected reference to find them. We could look into the index of library names, but it is not clear that the exposition-only names belong there.
It would be helpful to add a new index for all library concepts, including the exposition-only ones denoted by appearing in italics. It might also be useful to index the Cpp17Requirements, but most of those are reasonably easy to find today, and with a consistent prefix naming convention, perhaps better served by consistently adding them to the main index (where some, but not all, already reside).
The text was updated successfully, but these errors were encountered:
Editorial meeting: Nice idea. The index should contain exposition-only and published new-style (but not Cpp17) concepts. Only index definitions, not uses (too much work).
The standard library specification is filling up with concepts, especially "exposition only" concepts, and Cpp17Requirements. It is often necessary to locate the definition of these concepts to understand the clause you are reading, and there is no easy collected reference to find them. We could look into the index of library names, but it is not clear that the exposition-only names belong there.
It would be helpful to add a new index for all library concepts, including the exposition-only ones denoted by appearing in italics. It might also be useful to index the Cpp17Requirements, but most of those are reasonably easy to find today, and with a consistent prefix naming convention, perhaps better served by consistently adding them to the main index (where some, but not all, already reside).
The text was updated successfully, but these errors were encountered: