If this was merged into Rust, I assume it means the use of `unsafe` in std would be "pushed down" one level into Rustix instead.
Wonder if that means it would be easier to verify the correctness of `unsafe` use inside Rust itself?
Wonder if that means it would be easier to verify the correctness of `unsafe` use inside Rust itself?
> Wonder if that means it would be easier to verify the correctness of `unsafe` use inside Rust itself?
If you mean usage of unsafe inside std (which the Rust compiler does depend upon), that is one of the explicit goals of Rustix. The usage of unsafe will be much more narrow overall, mostly surrounding the system calls themselves.
In any case, I hope it remains separate. Third-party no_std code would benefit from it.
[1] Like a typical RTOS, that may provide some basic communication primitives, thread creation, and a hardware abstraction layer (HAL).
Libc is necessary, but not good.