Backport `Either` to 0.4

Open
#66 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust

Research direction

Start by reviewing issue #64 and the repository's current branch and release history to understand the introduced Either type and the 0.4 baseline. Backport the requested change to a 0.4 branch and verify that the resulting release makes Either available to crates still using that line.

Written by the indexing model from the issue text.

Description

With the latest changes, moving types to http-body-util, I think this will require a breaking change release for a lot of crates.

I have a use-case where I require the recently introduced Either type from #64, currently I basically just copied the file. Would it be possible to backport #64 to a 0.4 branch and make a release?

Happy to make the PR of course.

Dominant language
Rust
Stars
173
Forks
71
Avg merge
1d 12h
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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.

More from hyperium/http-body

All issues in hyperium/http-body

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.