Out of curiosity can you procure a GitHub link diffing the two projects? I’d like to see how much code is involved.
If we decide to merge support for the two I don’t think an RFC will be required. We routinely add platform support.
The main issues here in my opinion are:
The size of the patches. If the amount of code is comparable to a unix that is easier to consider than if the amount of comparable to the difference between unix/windows.
The amount of maintenance burden this will impose. Redox is under heavy development. I don’t want to see the rust-lang/rust PR queue overwhelmed by Redox churn. Rust contributors shouldn’t have to deal with that.
Not all OSes can have in-tree support from Rust. std is intended to be decomposed in a way that allows others to build on that work out-of-tree, though it does not fulfill that yet. That you are currently successfully overriding liblibc is great - that’s exactly how it should work. std itself though needs a great deal of refactoring to support this. I have previously outlined how I believe std should be architected to allow std to be reused out-of-tree for other OSes. As a high-profile, and active Rust project, Redox may be appropriate to support in-tree, but that’s not obvious; there will definitely be a lot of push back.