Synchronous IO with overlapped moves file pointer. #1309
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The documentation gives the impression that the file pointer of a synchronous file handle is updated by WriteFile/ReadFile only if lpOverlapped is NULL. In fact it is also updated if it is not NULL. That is surprising, because (1) in this case the operation doesn't use the file position itself, it uses the offset from the overlapped object instead, and (2) the documentation tells you it only updates the overlapped object afterwards (in contrast with respective earlier paragraphs about the NULL case). A reader might have the impression that this is a drop-in replacement for POSIX pread/pwrite, but it's not, due to this side-effect.
Example: