New issue
Advanced search Search tips

Issue 604787 link

Starred by 1 user

Issue metadata

Status: Archived
Owner:
Closed: Sep 27
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug



Sign in to add a comment

ReadAtCurrentPos() has different behavior between POSIX and Windows

Project Member Reported by joedow@chromium.org, Apr 19 2016

Issue description

This API is a bit confusing, there is a ReadAtCurrentPosNoBestEffort which states it won't guarantee that all bytes are read (non-blocking I/O) and ReadAtCurrentPos() which may or may not attempt to read all bytes depending on the platform.

It seems like it would be a good idea to fix the ReadAtCurrentPos() so that it reads all bytes unless there is an error for all supported platforms.

 

Comment 1 by joedow@chromium.org, Apr 19 2016

This issue was suggested by sergeyu in his comments for:
https://codereview.chromium.org/1900733002
Labels: M-53

Comment 3 by joedow@chromium.org, Jun 22 2016

Labels: -M-53 M-54

Comment 4 by joedow@chromium.org, Jul 12 2016

Labels: -M-54
Labels: OS-Linux
Status: Archived (was: Assigned)

Sign in to add a comment