You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, it's got cfg(unix), so then name "unix pipes" makes sense. The librustuv implementation supports windows named pipes, and the libnative implementation will soon also support named pipes.
This should probably be renamed to io::pipe or io::net::pipe (or something like that).
The text was updated successfully, but these errors were encountered:
There's a few parts to this PR
* Implement unix pipes in libnative for unix platforms (thanks @Geal!)
* Implement named pipes in libnative for windows (terrible, terrible code)
* Remove `#[cfg(unix)]` from `mod unix` in `std::io::net`. This is a terrible name for what it is, but that's the topic of #12093.
The windows implementation was significantly more complicated than I thought it would be, but it seems to be passing all the tests. now.
Closes#11201
Right now, it's got
cfg(unix)
, so then name "unix pipes" makes sense. The librustuv implementation supports windows named pipes, and the libnative implementation will soon also support named pipes.This should probably be renamed to
io::pipe
orio::net::pipe
(or something like that).The text was updated successfully, but these errors were encountered: