hyperium / hyperium/hyper

Unify Channel Dependency

Open
#3,309 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

B-upstream C-performance
Dominant language
Rust
Stars
16.3k
Forks
1.8k
Avg merge
1d 22h
Merged PRs (30d)
14

Description

Hyper currently depends on both futures_channel and tokio::sync, using both channel types in different places. To cut down on dependencies one of these should be removed.

Contributor guide

Open the contributing guide

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.

Research direction

Locate all uses of futures_channel and tokio::sync in Hyper and compare the channel types used in each area. Determine which dependency can be removed without changing behavior, update the affected channel usage consistently, and run the existing test suite to verify that the HTTP library still passes its tests.

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
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.