rust/src/libstd/sys/windows/net.rs, branch try
https://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=try
2020-07-28T00:51:13+00:00
mv std libs to library/
2020-07-28T00:51:13+00:00
mark
markm@cs.wisc.edu
2020-06-12T02:31:49+00:00
urn:sha1:2c31b45ae878b821975c4ebd94cc1e49f6073fd0
Migrate to numeric associated consts
2020-06-10T01:35:47+00:00
Lzu Tao
taolzu@gmail.com
2020-06-02T07:59:11+00:00
urn:sha1:fff822fead6249671cbcb090b24bce58fab38de0
Update name
2020-04-26T11:24:16+00:00
Steven Fackler
sfackler@gmail.com
2020-03-12T01:02:52+00:00
urn:sha1:07443f17d4c2e8135d1cbf415f6bd22eee86b64a
Add Read/Write::can_read/write_vectored
2020-04-26T11:23:39+00:00
Steven Fackler
sfackler@gmail.com
2020-01-03T19:26:05+00:00
urn:sha1:15262ec6be6fcfc9f27e174a0714d5a62e775fb0
When working with an arbitrary reader or writer, code that uses vectored
operations may end up being slower than code that copies into a single
buffer when the underlying reader or writer doesn't actually support
vectored operations. These new methods allow you to ask the reader or
witer up front if vectored operations are efficiently supported.
Currently, you have to use some heuristics to guess by e.g. checking if
the read or write only accessed the first buffer. Hyper is one concrete
example of a library that has to do this dynamically:
https://github.com/hyperium/hyper/blob/0eaf304644a396895a4ce1f0146e596640bb666a/src/proto/h1/io.rs#L582-L594
Use drop instead of the toilet closure `|_| ()`
2020-01-02T08:56:12+00:00
Lzu Tao
taolzu@gmail.com
2020-01-02T08:56:12+00:00
urn:sha1:dd8f07223346b06da723c25a3ac42f874e6c945c
Format the world
2019-12-22T22:42:47+00:00
Mark Rousskov
mark.simulacrum@gmail.com
2019-12-22T22:42:04+00:00
urn:sha1:a06baa56b95674fc626b3c3fd680d6a65357fe60
Require issue = "none" over issue = "0" in unstable attributes
2019-12-21T11:16:18+00:00
Ross MacArthur
ross@macarthur.io
2019-12-21T11:16:18+00:00
urn:sha1:f7256d28d1c2f8340ab5b99df4bdb15aa232f3f3
added correct error code for WSASocketW failure fallback
2019-12-02T18:12:51+00:00
avikozokin
kozokinavi@gmail.com
2019-12-02T18:12:51+00:00
urn:sha1:fa8b54901f1236cbcd48205856e8766496664105
std: win: Don't use SetHandleInformation on UWP
2019-07-25T19:30:08+00:00
Hugo Beauzée-Luyssen
hugo@beauzee.fr
2019-05-27T14:51:29+00:00
urn:sha1:a713a0399a6e63de1c8009a390ae964ff03f4067
Attempt to create sockets with the WSA_FLAG_NO_HANDLE_INHERIT flag, and
handle the potential error gracefully (as the flag isn't support on
Windows 7 before SP1)
Stabilized vectored IO
2019-04-27T15:34:08+00:00
Steven Fackler
sfackler@gmail.com
2019-04-27T15:34:08+00:00
urn:sha1:bd177f3ea31e47b94dd400239a9badfe2bd47355
This renames `std::io::IoVec` to `std::io::IoSlice` and
`std::io::IoVecMut` to `std::io::IoSliceMut`, and stabilizes
`std::io::IoSlice`, `std::io::IoSliceMut`,
`std::io::Read::read_vectored`, and `std::io::Write::write_vectored`.
Closes #58452