I’ve read that kind of perl-generated assembly and honestly it is also unreadable and unauditable. I decided not to go for it for the project I’m working on and

I’ve read that kind of perl-generated assembly and honestly it is also unreadable and unauditable. I decided not to go for it for the project I’m working on and use pure rust libraries. But note that you can write inline assembly in rust too[1] [1]: https://doc.rust-lang.org/1.8.0/book/inline-assembly.html https://doc.rust-lang.org/1.8.0/book/inline-assembly.html I’ve also used tooling[2] to measure any timing issues in libraries like dalek (ed25519) and it couldn’t find any (so good luck if you’re trying to exploit that over the network) [2]: https://github.com/rozbb/dudect-bencher https://github.com/rozbb/dudect-bencher Today I’d be more worried by memory safety bugs created by the use of C or assembly, or logic bugs due to only a few people being able to audit an implementation.