better benchmarks for new changes tracking issue

Open
  • Is something wrong?
#848 4 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
22/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
rust
Domain
performance

Research direction

The body names no files, tests or benchmarks, so there is no entry point yet. Start by reading the issue comments to see which benchmarks are already listed or wanted, then pick one specific missing or outdated case to propose. Done means one concrete benchmark is agreed on in the thread and added in a pull request.

Written by the indexing model from the issue text.

Description

good first issue help wanted tracking issue

New or improved benchmarks that are missing or need revision.

Dominant language
Rust
Stars
1.8k
Forks
244
Avg merge
1d 6m
Merged PRs (30d)
63

Getting set up

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 smallvec/smallvec

All issues in smallvec/smallvec

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.