dnrops
/
rfcs
mirror of https://github.com/rust-lang/rfcs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

RFC 980: read_exact

This commit is contained in:
Aaron Turon 2015-08-07 09:33:27 -07:00
parent 3edafbd8d1
commit 10ded18b7f
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
README.md
View File

@ -49,6 +49,7 @@ the direction the language is evolving in.
* [0909-move-thread-local-to-std-thread.md](text/0909-move-thread-local-to-std-thread.md)
* [0911-const-fn.md](text/0911-const-fn.md)
* [0968-closure-return-type-syntax.md](text/0968-closure-return-type-syntax.md)
* [0980-read-exact.md](text/0980-read-exact.md)
* [0982-dst-coercion.md](text/0982-dst-coercion.md)
* [0979-align-splitn-with-other-languages.md](text/0979-align-splitn-with-other-languages.md)
* [1011-process.exit.md](text/1011-process.exit.md)

7
text/0000-read-all.md → text/0980-read-exact.md
View File

@ -1,7 +1,7 @@
- Feature Name: read_exact and ErrorKind::UnexpectedEOF
- Feature Name: read_exact
- Start Date: 2015-03-15
- RFC PR: (leave this empty)
- Rust Issue: (leave this empty)
- RFC PR: https://github.com/rust-lang/rfcs/pull/980
- Rust Issue: https://github.com/rust-lang/rust/issues/27585
# Summary
@ -282,4 +282,3 @@ the following reasons:
compressed file where the uncompressed size was given in a header),
`read_full` has to always write to the output buffer, so there's not
much to gain over a generic looping implementation calling `read`.