mongodb / mongodb/mongo-rust-driver
RUST-1545 Consider removing the take_mut dependency
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.5k
- Forks
- 201
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 22
Description
Versions/Environment
- What version of Rust are you using?
Rust 1.65 - What operating system are you using?
N/A - What versions of the driver and its dependencies are you using? (Run
cargo pkgid mongodb&cargo pkgid bson)
Driver v2.3.1 - What version of MongoDB are you using? (Check with the MongoDB shell using
db.version())
N/A - What is your MongoDB topology (standalone, replica set, sharded cluster, serverless)?
N/A
Describe the bug
There is a potential memory leak in take_mut, which I noted from 2 issues filed with cargo-crev. A pull request with a fix was opened several years ago and it hasn't been merged yet, so the repository might also be rightly considered abandoned.
Is this dependency necessary? Something to consider, as it also uses unproven unsafe code.
https://github.com/yvt/crev-proofs and https://github.com/vorner/crev-proofs both reported issues.
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 tracing the take_mut dependency through the driver's Rust source and checking whether the reported upstream fix addresses the cargo-crev concerns. Done means determining whether it can be removed or safely replaced, with the driver's existing behavior preserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100