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.

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

Merged
merged 1 commit into from Nov 13, 2020

Conversation

jensmaurer
Copy link
Member

as directed by ISO/CS.

Partially addresses #4319

source/iostreams.tex Outdated Show resolved Hide resolved
source/iostreams.tex Outdated Show resolved Hide resolved
source/iostreams.tex Outdated Show resolved Hide resolved
@@ -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}.
Copy link
Member

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:

Suggested change
\tcode{absolute} can have the same semantics as \tcode{GetFullPathNameW}.
\tcode{absolute} typically has the same semantics as \tcode{GetFullPathNameW}.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

Copy link
Member

@jwakely jwakely Nov 16, 2020

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.

@@ -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
Copy link
Member

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:

Suggested change
global variable. It can be changed unexpectedly by third-party or system
global variable, and can be changed unexpectedly by third-party or system

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

@@ -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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

@jensmaurer
Copy link
Member Author

All fixed and force-pushed.

@zygoloid zygoloid merged commit c030451 into cplusplus:c++20 Nov 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants