Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upImplement read_exact for the Read trait #27588
Conversation
rust-highfive
assigned
huonw
Aug 7, 2015
This comment has been minimized.
This comment has been minimized.
|
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @huonw (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. The way Github handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
cesarb
referenced this pull request
Aug 7, 2015
Closed
Tracking issue for `read_exact` (RFC #980) #27585
sfackler
reviewed
Aug 8, 2015
| /// | ||
| /// If this function encounters an "end of file" before completely filling | ||
| /// the buffer, it returns an error of the kind `ErrorKind::UnexpectedEOF`. | ||
| /// The contents of `buf` are undefined in this case. |
This comment has been minimized.
This comment has been minimized.
sfackler
Aug 8, 2015
Member
Might want to say "unspecified" instead of "undefined" here to avoid conflating with undefined behavior.
sfackler
reviewed
Aug 8, 2015
| /// The contents of `buf` are undefined in this case. | ||
| /// | ||
| /// If any other read error is encountered then this function immediately | ||
| /// returns. The contents of `buf` are undefined in this case. |
This comment has been minimized.
This comment has been minimized.
sfackler
reviewed
Aug 8, 2015
| /// If any other read error is encountered then this function immediately | ||
| /// returns. The contents of `buf` are undefined in this case. | ||
| /// | ||
| /// If this function returns an error, it is undefined how many bytes it |
This comment has been minimized.
This comment has been minimized.
alexcrichton
reviewed
Aug 10, 2015
| /// # Ok(()) | ||
| /// # } | ||
| /// ``` | ||
| #[unstable(feature = "read_all", reason = "recently added")] |
This comment has been minimized.
This comment has been minimized.
alexcrichton
Aug 10, 2015
Member
Could you switch (and the above error kind variant) to use the read_exact feature instead?
This comment has been minimized.
This comment has been minimized.
|
Looking good to me, thanks @cesarb! Just one minor nit and I think this is good to go |
This comment has been minimized.
This comment has been minimized.
rust-highfive
assigned
alexcrichton
and unassigned
huonw
Aug 10, 2015
This comment has been minimized.
This comment has been minimized.
|
Oh oops, sorry for the delay @cesarb! Feel free to ping a PR whenever it's updated as unfortunately github doesn't send out notifications for force-pushes or new commits. As one final thing, could you squash these commits together? Thanks! |
cesarb
force-pushed the
cesarb:read_all
branch
from
f88eda8
to
ff81920
Aug 24, 2015
This comment has been minimized.
This comment has been minimized.
Done. Do you need me to also rebase this on top of a more recent master?
Sorry, I hadn't noticed that. I'll make sure to write a dummy comment whenever I update a pull request from now on. |
This comment has been minimized.
This comment has been minimized.
|
@bors r=alexcrichton |
This comment has been minimized.
This comment has been minimized.
|
|
This comment has been minimized.
This comment has been minimized.
|
|
bors
added a commit
that referenced
this pull request
Aug 25, 2015
This comment has been minimized.
This comment has been minimized.
|
|
This comment has been minimized.
This comment has been minimized.
|
Looks like
|
This comment has been minimized.
This comment has been minimized.
|
There seems to be a catch-22 here:
What should be done to break this deadlock? |
This comment has been minimized.
This comment has been minimized.
|
Ah feel free to use the RFC tracking issue, #27585, for the issue number |
This comment has been minimized.
This comment has been minimized.
|
I made a commit adding the issue number to the unstable declarations, and it seems to have been accepted by travis-ci. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
bors
added a commit
that referenced
this pull request
Aug 29, 2015
This comment has been minimized.
This comment has been minimized.
|
|
This comment has been minimized.
This comment has been minimized.
|
@bors retry |
This comment has been minimized.
This comment has been minimized.
bors
added a commit
that referenced
this pull request
Aug 30, 2015
This comment has been minimized.
This comment has been minimized.
|
|
This comment has been minimized.
This comment has been minimized.
|
@bors retry |
cesarb commentedAug 7, 2015
This implements the proposed "read_exact" RFC (rust-lang/rfcs#980).
Tracking issue: #27585