Like time-constant, and it's hard to be time-constant in a performance optimised language like Rust. LLVM is doing some magic, and you don't want any magic in a crypto library.
If you want a safe interface that does not require passing random sizes around in extra arguments, this can also be done in C.
On Rust, it's pure love in 64 bit, I acknowledge that (I use Cosmic DE with Pop!_OS so I can relate) and evcode it's my main IDE, Crabcraft being second. But compiling 'simple' TUI tools on Rust it's impossible on 32 bit, even with ZRAM and a total of 1.5GB of RAM.
If you want half-secure TUI tools on 32 bit Golang it's a saner option than C/C++, for instance AERC can be safer than Mutt to read email, even under a Maildir mailbox and email fetched/sent with isync/msmtp.
Meanwhile, ring [2] carries an explicit disclaimer of "This is an experiment".
Things like the dumb (not like I'm any individual being dumb. Just collective accumulated stupidity) a*hole vulnerability some weeks ago. That wasn't even performance sensitive.
Rust fixes it.