ReadAtCurrentPos() has different behavior between POSIX and Windows |
|||||
Issue descriptionThis 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.
,
May 4 2016
,
Jun 22 2016
,
Jul 12 2016
,
Sep 27
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by joedow@chromium.org
, Apr 19 2016