bed-reader VS pariter

I have trouble remembering the direct syntax for iterators and arrays. So, the macro is especially useful using when nesting inside them. For example, in the bed-reader genomics crate, I was apply to replace dozens of functions like:

I'm creating a genomics-related crate. When a user asks for a field of a struct, I clone it. If the field is never used again, then an optimizer could move instead of clone. Can I expect this to happen?

Thanks! That works great and is now checked in.

u/HeroicKatora, in Python I use Pooch to create a function called "sample_file" that returns the path to a sample file. (Behind the scenes, it downloads the file if needed). The function lets me write Python usage examples like this:

How much does this matter? Here are benchmarks from fastlmm/bed-reader at bed-writer (github.com):

For our Bed-Reader open-source genomics tool, it would be great to speed up writing to a file. Writing is usually CPU-bound because each column of a big array (for example, 1M x 100) must be processed before output. A single-threaded, simplified writer is below and on the Rust Playground.

Thank you Rust & Rayon for letting Bed-Reader escape from C++/OpenMP runtime compatibility hell!

Once you have something working, and you want to make it fast, run cargo install flamegraph, and then cargo flamegraph, to see where your code is spending its time. Once you've fixed any hot spots that you weren't expecting, you can try using rayon or https://github.com/dpc/pariter to start making use of more CPU cores.

Parallel iterators: rayon or what I ended up using because I wanted to keep the original order is this amazing library: https://github.com/dpc/pariter

There is also https://github.com/dpc/pariter which is similar to rayon but preserves order of tasks.

All right, I've got it working. https://github.com/dpc/pariter/tree/non-static-f