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

[dcl.attr.*] and Recommended Practice #2978

Closed
AaronBallman opened this issue Jul 19, 2019 · 1 comment · Fixed by #3628
Closed

[dcl.attr.*] and Recommended Practice #2978

AaronBallman opened this issue Jul 19, 2019 · 1 comment · Fixed by #3628
Assignees
@jensmaurer

Comments

@AaronBallman
Copy link
Contributor

One of the tools the C standard uses for its attribute wording is a Recommended Practice section (http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2385.pdf 6.7.11). These sections correspond to the same wording we put in informative notes currently.

From what I understand, a Recommended Practice is a special kind of section (like Constraints or Semantics) that places normative encouragement on implementations without being a normative requirement. Would it make sense to follow suit in C++? I think it may allow us to speak more authoritatively than a note while still serving the purpose of not being a normative requirement.
@jensmaurer jensmaurer added the decision-required A decision of the editorial group (or the Project Editor) is required. label Aug 9, 2019
@jensmaurer jensmaurer removed the decision-required A decision of the editorial group (or the Project Editor) is required. label Sep 10, 2019
@jensmaurer jensmaurer added the decision-required A decision of the editorial group (or the Project Editor) is required. label Sep 24, 2019
@jensmaurer
Copy link
Member

Editorial meeting: De-note those things and use "should". Like a library element, have a "Recommended practice" paragraph introducer. (Describe that element.) Have CWG review the change.

@jensmaurer jensmaurer removed the decision-required A decision of the editorial group (or the Project Editor) is required. label Oct 21, 2019
@jensmaurer jensmaurer mentioned this issue Jan 13, 2020
Merged
@jensmaurer jensmaurer self-assigned this Jan 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jensmaurer jensmaurer

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[dcl.attr] Introduce 'Recommended practice' paragraphs. jensmaurer/draft
2 participants
@AaronBallman @jensmaurer