Implement Send for libgit2 structs
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2.1k
- Forks
- 450
- Avg merge
- 11m
- Merged PRs (30d)
- 1
Description
According to the libgit2 docs, it it safe to use objects on a thread other than the one they are created on (though there are some special considerations for older versions of OpenSSL). As such, it should be safe to implement Send (but not Sync) for all core libgit2 structs (Commit, Author, etc).
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 reading the linked libgit2 THREADING.md documentation and inspecting the core libgit2 structs named in the issue, including Commit and Author. Determine which structs can safely be moved between threads while remaining non-Sync, accounting for the OpenSSL version consideration. Done means the applicable structs implement Send without implementing Sync.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100