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
[input.output] Replace 'could' and 'might' #4346
Conversation
source/iostreams.tex
Outdated
@@ -15201,7 +15202,7 @@ | |||
For POSIX-based operating systems, | |||
\tcode{absolute(p)} is simply \tcode{current_path()/p}. | |||
For Windows-based operating systems, | |||
\tcode{absolute} might have the same semantics as \tcode{GetFullPathNameW}. | |||
\tcode{absolute} can have the same semantics as \tcode{GetFullPathNameW}. |
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 don't think we're talking about ability or capability here; rather, we're talking about possibility. Given https://github.com/microsoft/STL/blob/master/stl/inc/filesystem#L3001, I think we can be so bold as to say:
\tcode{absolute} can have the same semantics as \tcode{GetFullPathNameW}. | |
\tcode{absolute} typically has the same semantics as \tcode{GetFullPathNameW}. |
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.
fixed
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.
Ahem, there are two implementations that support Windows :-) But the other one also uses GetFullPathNameW
here.
source/iostreams.tex
Outdated
@@ -15762,7 +15763,7 @@ | |||
\pnum | |||
\begin{note} | |||
The current path as returned by many operating systems is a dangerous | |||
global variable. It might be changed unexpectedly by third-party or system | |||
global variable. It can be changed unexpectedly by third-party or system |
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.
The second sentence isn't true in isolation -- we don't know that it can be changed asynchronously. How about this:
global variable. It can be changed unexpectedly by third-party or system | |
global variable, and can be changed unexpectedly by third-party or system |
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.
fixed
source/iostreams.tex
Outdated
@@ -15789,7 +15790,7 @@ | |||
\pnum | |||
\begin{note} | |||
The current path for many operating systems is a dangerous | |||
global state. It might be changed unexpectedly by a third-party or system | |||
global state. It can be changed unexpectedly by a third-party or system |
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.
global state. It can be changed unexpectedly by a third-party or system | |
global state, and can be changed unexpectedly by a third-party or system |
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.
fixed
source/iostreams.tex
Outdated
A postcondition of \tcode{last_write_time(p) == new_time} is not specified since it might not hold for file systems | ||
with coarse time granularity. | ||
A postcondition of \tcode{last_write_time(p) == new_time} is not specified | ||
since it does not necessarily hold for file systems with coarse time granularity. |
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.
since it does not necessarily hold for file systems with coarse time granularity. | |
because it does not necessarily hold for file systems with coarse time granularity. |
(Drive-by: use "since" only when dealing with time, and "because" for causality.)
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.
fixed
as directed by ISO/CS.
All fixed and force-pushed. |
as directed by ISO/CS.
Partially addresses #4319