5 ms·

FWIW, RustCrypto is neither written in safe rust or only rust. It uses inline assembly, unsafe byte manipulation, and unsafe intrinsics

• snickerbockers 3y ago
  You're not going to get good performance any other way.
• Grimburger 3y ago
  > unsafe intrinsics You mean like AESENC which you should always be using if available? The rust fanclub obsession with calling things like that unsafe simply because it has the same keyword in front of it is fairly ridiculous. > inline assembly Sometimes it's the only way to get some sort of constant time guarantees.
  • conradludgate 3y ago
    > You mean like AESENC which you should always be using if available? Yes. And make it not unsafe > Sometimes it's the only way to get some sort of constant time guarantees I don't think you understood the article then. Brian wants the constant time guarantees as an intrinsic in the std library, guaranteed by the compiler, and exposed as safe rust. > The rust fanclub obsession with calling things like that unsafe simply because it has the same keyword in front of it is fairly ridiculous. If you have to use the unsafe keyword, you're creating the possibility of memory safety vulnerability. It would be amazing if you could immediately see that all code in a library does not use unsafe and know an entire class of vulnerabilities does not exist
    • Grimburger 3y ago
      > Yes. And make it not unsafe That's simply not possible, all intrinsics are unsafe by definition, the rust compiler can't check them for the same guarantees.