Comment on Compiling typed Python: types are very broad hints and they are sometimes lies.
Turun@feddit.de 9 months agoI never used C, so I don’t know how easy it is there.
In rust there is a library that takes care of all the details (PyO3), so you only need to add #[pyclass] or #[pymethod] above your structs and methods, define what the module/submodule/classes/functions is and run the tool provided by the PyO3 library to compile the code and install it in a local virtual environment.
So it’s literally (the actual meaning of literally) just two lines for every class or method you want to have available in python and ten lines in the Cargo.toml/pyproject.toml config files.
This article shows the basic usage.
UlrikHD@programming.dev 9 months ago
Interesting stuff, might give me an excuse to look into rust in the future. Thanks!
Turun@feddit.de 9 months ago
I personally did one project with PyO3 and it was a breeze.
For data analysis I initially implemented my physics model in python (say f=m*a), but during a fitting procedure (what is “a”, given a measured “m” and “f”?) this part of the code is called thousands of times.
Writing such a simple function is rust (twi numbers in (m and a guess for a), one number out (predicted f)) was easy. Since there are no complex data structures involved the borrow checker was happy the whole way through. Rust has bindings for numpy with the ndarray crate/library, so even that was simple.
Simply writing the numerics in rust gave a 40x speedup in my case. I got another 2.5x by making the main loop of my calculation parallel. With the rayon crate this is again a single line change, turning
for x in array {…}intofor x in array.par_iter() {…}