Rust-only fixtures for getting array data
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 80
- Forks
- 8
- Avg merge
- 21h 44m
- Merged PRs (30d)
- 5
Description
We currently do not unit-test in rust because the calling python code can do this for us, but this can make development a bit slow because you have to recompile every time via maturin develop before running tests, which is error-pronce.
Another advantage of setting up "fixture" that look like the python requests is to be able to benchmark within rust only.
In other words we should create inputs to https://github.com/ilan-gold/zarrs-python/blob/d29343b6ab2762e6dc7f0186217ecc8fe1f85fba/src/array.rs#L414 as if they were actually coming from python, but purely in rust.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at src/array.rs around line 414 and inspect how Python requests reach that entry point. Review the existing test setup and the maturin develop workflow, then add Rust-only inputs that mirror the Python requests so they can be tested and benchmarked without rebuilding the Python extension for each run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, rust
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100