memorysafety / memorysafety/rav1d
Add C API tests
Open
Nobody has claimed this yet.
testing
- Dominant language
- Assembly
- Stars
- 643
- Forks
- 81
- PR merge metrics
- No merged PRs in 30d
Description
rav1d needs to be a drop-in replacement for dav1d, which means we need to keep the public C API intact as we refactor the transpiled Rust code. In order to ensure that we don't accidentally make changes to the public API, we should write some basic tests that use the C API and verify that it continues to function as expected.
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 by locating rav1d's public C API and the existing test infrastructure, then review how the transpiled Rust code exposes that API. Done means basic tests exercise the public C API and verify that its expected behavior remains compatible with dav1d.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, rust
- Domain
- api, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100