Skip to content

[concepts] Use "model" instead of "satisfy" for the semantic requirements #2591

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.

Sign up for GitHub

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

Jump to bottom
Closed
JohelEGP opened this issue Dec 11, 2018 · 2 comments · Fixed by #2797
Closed

[concepts] Use "model" instead of "satisfy" for the semantic requirements #2591

JohelEGP opened this issue Dec 11, 2018 · 2 comments · Fixed by #2797
Assignees
@CaseyCarter

Comments

@JohelEGP
Copy link
Contributor

See #2176 (comment).
@jensmaurer
Copy link
Member

See also #1263.

@jensmaurer
Copy link
Member

@CaseyCarter, are you intending to eventually submit a patch for this area of concern?

CaseyCarter added a commit to CaseyCarter/draft that referenced this issue Jan 6, 2019
@CaseyCarter
Library-wide: Consistently use "models"/"meets" for concept/non-conce…
483a28f 
…pt requirements

...and use "satisfies" only with pure predicates  - those without semantic requirements - including concepts when only the syntactic requirements are intended.

Fixes cplusplus#2591.
CaseyCarter added a commit to CaseyCarter/draft that referenced this issue Jan 6, 2019
@CaseyCarter
Library-wide: Consistently use "models"/"meets" for concept/non-conce…
09cc8ac 
…pt requirements

...and use "satisfies" only with pure predicates  - those without semantic requirements - including concepts when only the syntactic requirements are intended.

Fixes cplusplus#2591.
@CaseyCarter CaseyCarter mentioned this issue Jan 6, 2019
Closed
CaseyCarter added a commit to CaseyCarter/draft that referenced this issue Jan 7, 2019
@CaseyCarter
[customization.point.object,concepts,range.semi.wrap] Use "model" ins…
95e5be9 
…tead of "satisfy" with library concept requirements

Fixes cplusplus#2591.
CaseyCarter added a commit to CaseyCarter/draft that referenced this issue Mar 17, 2019
@CaseyCarter
Library-wide: Use "model" instead of "satisfy" with library concept r…
1d18818 
…equirements

Updates: [structure.requirements],[customization.point.object],[res.on.requirements],[concepts], and [range.semi.wrap].

Fixes cplusplus#2591.
@CaseyCarter CaseyCarter mentioned this issue Mar 17, 2019
Merged
CaseyCarter added a commit to CaseyCarter/draft that referenced this issue Mar 17, 2019
@CaseyCarter
Library-wide: Use "model" instead of "satisfy" with library concept r…
fd8088c 
…equirements

Updates: [structure.requirements],[customization.point.object],[res.on.requirements],[concepts], and [range.semi.wrap].

Fixes cplusplus#2591.
CaseyCarter added a commit to CaseyCarter/draft that referenced this issue Mar 17, 2019
@CaseyCarter
Library-wide: Use "model" instead of "satisfy" with library concept r…
77be157 
…equirements

Updates: [structure.requirements],[customization.point.object],[res.on.requirements],[concepts], and [range.semi.wrap].

Fixes cplusplus#2591.
zygoloid pushed a commit that referenced this issue Jun 14, 2019
@CaseyCarter @zygoloid
[library-wide] Use "model" instead of "satisfy" for semantic library …
b3b1f63 
…concept requirements

Consistently use "satisfy" to mean the syntactic requirements are met, and "model" to mean the semantic requirements are met.

Updates: [structure.requirements],[customization.point.object],[res.on.requirements],[concepts], and [range.semi.wrap].

Fixes #2591.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@CaseyCarter CaseyCarter

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Library-wide: Use "model" instead of "satisfy" with library concept r… CaseyCarter/draft
3 participants
@CaseyCarter @JohelEGP @jensmaurer