Skip to content
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

[lib] Use \exposconcept and \libconcept where applicable #3494

Closed
jensmaurer opened this issue Nov 19, 2019 · 4 comments · Fixed by #3496
Closed

[lib] Use \exposconcept and \libconcept where applicable #3494

jensmaurer opened this issue Nov 19, 2019 · 4 comments · Fixed by #3496
Assignees

Comments

@jensmaurer
Copy link
Member

jensmaurer commented Nov 19, 2019

Inspect \tcode{\placeholder{...}} situations and other mentions of concept names that should use \exposconcept or \libconcept.

This is fuel for the already-existing index of concept names.

@jensmaurer jensmaurer changed the title [lib] Use \exposconcept where applicable [lib] Use \exposconcept and \libconcept where applicable Nov 20, 2019
@jensmaurer jensmaurer self-assigned this Nov 20, 2019
@zygoloid zygoloid added the decision-required A decision of the editorial group (or the Project Editor) is required. label Nov 21, 2019
@zygoloid
Copy link
Member

zygoloid commented Nov 21, 2019

Once we get a fully-concept-constrained standard library, we will have a lot of mentions of common concepts. Is indexing all of them useful?

Example: there are 95 mentions of is_constructible* in the standard library. Most of them will likely become constraints at some point. Is it useful to have 95 index entries for the constructible_from concept?

@jensmaurer
Copy link
Member Author

If not, what are the rules when to index concept uses (the concept definition is obvious, of course)?

@jensmaurer
Copy link
Member Author

Sample of concepts index after #3496
concepts

@jensmaurer
Copy link
Member Author

Editorial meeting: LWG chair says the big index is desirable. Let's go for it.

@jensmaurer jensmaurer removed the decision-required A decision of the editorial group (or the Project Editor) is required. label Feb 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants