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
[enum.copy_options] Rephrase restriction on copy_options values. #1445
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As I said in #1422 I think this is more precise, but seems clumsy. I wish we had a better way to say it.
Use bitmask 'element' phrasing for restrictions on copy_options. Fixes cplusplus#1445.
As discovered in #1422, it turns out that the requirements are already spelled out with the two function families that use copy_options. My new patch simply removes the general requirement and slightly adjusts the requires clauses with the individual functions. |
@jwakely: What do you think? |
Hmm, one is "from each |
Use bitmask 'element' phrasing for restrictions on copy_options. Fixes cplusplus#1445.
Rebased. |
Looks good to me. |
Use bitmask 'element' phrasing for restrictions on copy_options. Fixes cplusplus#1445.
Now also addressing @timsong-cpp's comment. |
Fixes #1422.