surface readable diagnostics from eager algorithms
Open
Nobody has claimed this yet.
enhancement
P1
- Dominant language
- C++
- Stars
- 2.4k
- Forks
- 270
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 39
Description
This has already been done for sync_wait, but it needs to be done for any sender consumer algorithm that eagerly connect-s the input sender(s). This includes:
sync_wait_with_variantensure_startedstart_detachedsplitasync_scope::spawn[_future]
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 by examining the existing sync_wait implementation and its diagnostics, then locate the eager connect paths for sync_wait_with_variant, ensure_started, start_detached, split, and async_scope::spawn[_future]. Done means each listed consumer surfaces readable diagnostics consistently; the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100