4 ms·
I’m the author of the package in question, so I can try to answer that. The first (and lazy) answer is that it was an educational exercise: I wanted to try my
by woodruffw 5y ago
I’m the author of the package in question, so I can try to answer that.
The first (and lazy) answer is that it was an educational exercise: I wanted to try my hand at writing in Python package in Rust, and this particular need afforded itself of me.
The second answer is that the package in question contains a (basic) parser, and it’s my opinion that Rust is particularly well suited to this domain: you should ideally only write a /proc/…/maps parser exactly once, with strong modeling of all valid and invalid states. Rust gives us that strong modeling for free (to say nothing of performance and memory safety), and it binds easily to other languages.