Base_64 VS rustix

Here's a Base64 encoder/decoder I did several years ago, teaching myself the very basics of using SPARK. It's a bit less aesthetic than I'd like, but I think it does show how [relatively] easy it is to incorporate some level of correctness-proof.

It would be great for Rust to have a Linux target that doesn't use libc, but from what I've read, not many people are interested in this.

Found this as well: https://github.com/sunfishcode/mustang

Some discussion here: https://github.com/bytecodealliance/rustix/issues/76

Without actually having looked into this, how does https://github.com/bytecodealliance/rustix fit into points 1 & 2?

I find this github issue: https://github.com/bytecodealliance/rustix/issues/575

Hi Rust experts, we are willing to integrate rustix on NuttX RTOS, the initial effort was done by rustix author: https://github.com/bytecodealliance/rustix/tree/nuttx but it hit the wall since we don't know the right way to integrate cargo with the old-school NuttX's Makefiles. Any help or suggestion is welcome. More about NuttX here: https://nuttx.apache.org and here: https://nuttx.apache.org/docs/latest/

Have you considered using rustix? It provides many of the facilities of std without using libc.

rustix can make syscalls directly to Linux. There's a rustc fork that can use it to build std.

The rustix project claims to use raw syscalls (and vDSO calls) on linux and provides more memory / type safety compared to the libc API.

Hi, the reason is explained by the description of https://github.com/bytecodealliance/rustix.

Please consider rustix as an alternative to nix.