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.

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

use return-type-requirements where applicable #2507

Closed
zygoloid opened this issue Nov 26, 2018 · 0 comments
Closed

use return-type-requirements where applicable #2507

zygoloid opened this issue Nov 26, 2018 · 0 comments
Labels
after-motions Pull request is to be applied after the pending edits from WG21 straw polls have been applied.
Milestone
post-2018-11

Comments

@zygoloid
Copy link
Member

P1084 instructs us to perform a transformation across the draft:

5.2 Throughout Clause [concepts], apply the revised interpretation of a return-type-requirement.

  • Replace each constraint of the form E; requires Concept<decltype((E))>; by the now-equivalent form { E } -> Concept;.
  • Replace each constraint of the form E; requires Concept<decltype((E)), Args...>; by the now-equivalent form { E } -> Concept<Args...>;.

This has been done for the pre-existing instances, but we're adding more as part of 2018-11 LWG Motion 25 (and maybe others?).
@zygoloid zygoloid added this to the post-2018-11 milestone Nov 26, 2018
@zygoloid zygoloid added the after-motions Pull request is to be applied after the pending edits from WG21 straw polls have been applied. label Nov 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
after-motions Pull request is to be applied after the pending edits from WG21 straw polls have been applied.
Projects
None yet
Milestone
post-2018-11
Development

No branches or pull requests
1 participant
@zygoloid