Not sure if this is the right place to discuss this, but I’ve been messing around with a kernel in Rust for a while now, and would like to start experimenting with trying to get a Rust program running in userspace. So far, I’ve added a new target to
rustc and done a little work (such as some stuff in
liballoc_system and whatnot - I don’t think this’ll ever get upstreamed but I can always hope ).
However, I don’t really want to end up with a
libc implementation in my userspace. I’ve begun porting
libstd, and noticed that a lot of stuff just calls the equivalent function in
libc. While I’m more than willing to reimplement these functions in
libstd directly in Rust, I’m now a little worried about how difficult porting crates that directly depend on
libc will be - would it be better to just bite the bullet and maintain a fork of something like
relibc. Am I asking for trouble in trying to avoid
libc, or is there any interest in avoiding it on platforms where it isn’t needed?