inout: improve test coverage

Open
  • Is something wrong?
#1,562 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
testing

Research direction

Start by locating the inout crate and reviewing its unsafe code and existing tests. Run the current test suite, then use Miri to check the tests. Done means meaningful tests cover the unsafe behavior and pass under Miri; the issue does not name specific code paths or expected cases.

Written by the indexing model from the issue text.

Description

The crate contains a fair amount of unsafe code, but number of tests is quite small. We should work on improving test coverage and run it in Miri.

Dominant language
Rust
Stars
688
Forks
177
Avg merge
2h 31m
Merged PRs (30d)
31

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from RustCrypto/utils

All issues in RustCrypto/utils

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.