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

[structure.specifications] Should we add an element for semantic requirements of concepts? #4491

Open
frederick-vs-ja opened this issue Feb 10, 2021 · 2 comments

Comments

@frederick-vs-ja
Copy link
Contributor

There are many semantic requirements of form "... type(s) model(s) some concept only if..." in specifications of standard concepts. However, as mentioned in #4054, there are also semantic requirements not of such form, and there are cases where semantic requirements are separated into different bullets (e.g. [iterator.concept.random.access]).

Should we add the "semantic requirements" element and specify semantic requirements consistently by it?

@jensmaurer jensmaurer added the decision-required A decision of the editorial group (or the Project Editor) is required. label Feb 10, 2021
@jensmaurer jensmaurer removed the decision-required A decision of the editorial group (or the Project Editor) is required. label Apr 16, 2021
@jensmaurer
Copy link
Member

Editorial meeting 2021-04-16: This seems to be paper-level material.

@jwakely , do you want to create an LWG issue for this?

@tkoeppe
Copy link
Contributor

tkoeppe commented Apr 16, 2021

We're definitely sympathetic to the idea, but it needs someone to drive this.

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

No branches or pull requests

3 participants