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
[std] Reword "cannot" in notes to not sound like negative permission #6770
base: main
Are you sure you want to change the base?
Conversation
This is about half of it, more to come shortly! |
Second half is in. PTAL. |
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.
I think the "cannot -> never" changes are readable and sometimes an improvement; "cannot -> it is not possible" changes are ugly. But so be it.
@@ -500,7 +500,7 @@ | |||
\begin{note} | |||
Because facets are used by iostreams, | |||
potentially while static constructors are running, | |||
their initialization cannot depend on programmed static initialization. | |||
it is not possible for their initialization to depend on programmed static initialization. |
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.
What is programmed static initialization?
which can be a different thread | ||
than the one that registered it, so registered functions cannot rely on the identity | ||
of objects with thread storage duration. | ||
which can be a different thread than the one that registered it, |
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.
"can"?
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.
How about "is invoked in the thread that calls at_quick_exit
, a possibly different one than the one that registered it"?
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.
calls quick_exit not at_quick_exit, and maybe "a possibly different thread than the one" to avoid "one than the one".
Notes shall not contain permissions. Even though "cannot" is allowed to express negative possibility, ISO has requested that we avoid it when it might be ambiguous and could be mistaken as permission.
This is so that notes do not (inappropriately) state requirements or permissions.
@@ -8638,7 +8637,7 @@ | |||
\pnum | |||
\begin{note} | |||
Except for reference and pointer types, a major array bound is not part of a | |||
function parameter type and cannot be deduced from an argument: | |||
function parameter type and is not possible to be deduced from an argument: |
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.
function parameter type and is not possible to be deduced from an argument: | |
function parameter type and it is not possible for it to be deduced from an argument: |
This seems a bit nicer to me
Notes shall not contain permissions. Even though "cannot" is allowed to express negative possibility, ISO has requested that we avoid it when it might be ambiguous and could be mistaken as permission.