Windows support

[Vizonex]

Hi, if you don't know who I am. I am the main founder of the winloop project and I think I could provide you with a bit of input for adding in windows support. Otherwise I would be willing to help with developing it in. Please know my knowledge of rust is a little bit on the beginner side but I should have no problem navigating this project once I get a grip on the program's architecture. I have already let my friend who is the main owner of the anyio project know I wanted to add this one in the future.

[gi0baro]

Hey @Vizonex, thank you for showing up and sorry for the late reply.

I'd say nothing really prevents adding Windows support to RLoop, it's just other priorities are scheduled – tbh, I'd rather want to see 1:1 parity with stdlib before adding more platform support – like SSL.
In theory mio supports windows, so it would be mainly a matter of gating the difference behind #[cfg(windows)] flags, add the relevant variants to the Python code, and test the whole thing on Windows – unfortunately I don't have any stable windows system to develop on, and even if I did, I feel like I won't have the time to focus on that.
Thus, if you want to contribute to RLoop in that regards, you're absolutely welcome to do so, at any pace you feel is right.

The general behaviour of RLoop, independently of the Rust language usage, is very similar to the stdlib asyncio module, thus if you're familiar with the CPython source code of that module I'd say it won't be too hard to navigate RLoop source code.

In regards of the anyio thing: RLoop acts as a replacement of the stdlib event loop, in the same way uvloop does, thus afaik anyio should work with RLoop out of the box, as it respects all asyncio interfaces – at least the ones implemented.