run `may_dangle` benchmarks on v2
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.7k
- Forks
- 216
- Avg merge
- 17h 50m
- Merged PRs (30d)
- 95
Description
we are trying to assess what performance benefits does may_dangle have
run cargo bench and cargo bench --features may_dangle, and open a PR with no changes and the table as description
if there are barely any / no performance improvements, maybe we should just remove it instead of having arbitrary features with no ROI
if benchmarks don't really reflect the use case where this feature might perform better, add some bench for it that shows that it makes a difference, if you can find one
Contributor guide
No contributing guide indexed for this repository
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 running cargo bench and cargo bench --features may_dangle on the v2 code, then compare their benchmark tables. Open a PR with no code changes and the results in its description; if the existing benchmarks do not represent the relevant use case, add a focused benchmark only when you can identify one that demonstrates a difference.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- performance
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100