Why does `SignatureVerificationAlgorithm` have a `Send + Sync` supertrait bound?
Open
Nobody has claimed this yet.
next-major-release
- Dominant language
- Rust
- Stars
- 39
- Forks
- 51
- PR merge metrics
- No merged PRs in 30d
Description
Why does SignatureVerificationAlgorithm have a Send + Sync supertrait bound?
https://github.com/rustls/pki-types/blob/1bc73dcdb53dd02c7b164d7bb235971b3374bd75/src/lib.rs#L891
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 at the cited definition in src/lib.rs around line 891 and read the six-comment discussion for the reason behind the Send + Sync supertrait bound. Compare the trait’s intended usage with the surrounding API, then document or resolve the rationale so the bound’s necessity is clear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cryptography, security
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100