# Proposal: make UnixStream \*type\* available on Windows

**URL:** https://internals.rust-lang.org/t/proposal-make-unixstream-type-available-on-windows/12427
**Category:** Uncategorized
**Created:** [May 26, 2020, 12:18am UTC](https://internals.rust-lang.org/t/proposal-make-unixstream-type-available-on-windows/12427 "2020-05-26T00:18:05Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![cuviper](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/cuviper/32/1897_2.png) [@cuviper](https://internals.rust-lang.org/u/cuviper)
#### Post date: [May 26, 2020, 12:59am UTC](https://internals.rust-lang.org/t/proposal-make-unixstream-type-available-on-windows/12427/3 "2020-05-26T00:59:58Z")

</div>

I assume you mean `UnixStream`? There's another recent thread, though no real conclusion...

> [@UnixStream on Windows?](https://internals.rust-lang.org/t/unixstream-on-windows/12305):
>
> [Recent Windows releases support AF\_UNIX stream sockets](https://devblogs.microsoft.com/commandline/af_unix-comes-to-windows/). However, std::os::unix::{UnixStream, UnixListener} are only available on Unix OSes. It would be useful to have these available on Windows as well so that developers don't have to pull in external crates to get functionality on Windows that's available in std for Unix. Is that assertion in line with the current thinking about what goes in std? If so, what's the best way to go about resolving this? It seems that we would have to move UnixSt…

---

_[View the full topic](https://internals.rust-lang.org/t/proposal-make-unixstream-type-available-on-windows/12427)._