pub fn read<P: AsRef<Path>>(path: P) -> io::Result<Vec<u8>> {
fn inner(path: &Path) -> io::Result<Vec<u8>> {
let mut file = File::open(path)?;
let mut bytes = Vec::new();
file.read_to_end(&mut bytes)?;
Ok(bytes)
}
inner(path.as_ref())
}
"aBsTraCtiOnS aRe gOod"... Right.Reference implementations must NOT have abstractions like this. Rust encourages it. Lots of Rust codebase is filled with them. Your feelings for Rust is irrelevant. C is simple and easy to understand, therefore reference implementations must be in C. Period.
...or Common Lisp, or OCaml... why not?!
(b) the equivalent C code would look pretty similar.
(c) this is not cryptographic code
https://github.com/ioccc-src/winner/blob/master/2024/burton/...
This code is fairly easy to understand, too, then.
(b) No, it would definitely not look "pretty similar".
(c) So what? You talked about abstractions in cryptographic code. Abstractions are layers to hide things. That is bad in crypto code.
In fact there have been many crypto bugs which insufficiently abstract this kind of stuff away.
Feel free to post your challenge snippet.