receivers shouldn't be parameterized on the sender
Open
Nobody has claimed this yet.
enhancement
good-first-issue
- Dominant language
- C++
- Stars
- 2.4k
- Forks
- 270
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 39
Description
The type can simply be parameterized on the value/error types.
The following algorithms have receivers that are parameterized on the sender:
-
split -
ensure_started -
stopped_as_[xxx] -
on -
into_variant
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
Locate the implementations and tests for split, ensure_started, stopped_as_[xxx], on, and into_variant. First inspect how each receiver is parameterized and how its sender type is used; done means all five receivers are parameterized only on value and error types, with the relevant tests still passing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100