swift-server / swift-server/swift-http-server
Investigate if async reader/async writer and their concluding variants should be sendable
Open
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 44
- Forks
- 13
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 8
Description
Investigate if async reader/async writer and their concluding variants should be sendable.
The concrete case when you hit it is when calling requestConcludingAsyncReader.consumeAndConclude { reader in and need to send the reader.
Contributor guide
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 tracing requestConcludingAsyncReader.consumeAndConclude and the async reader, async writer, and concluding variants mentioned in the issue. Determine whether these types should be Sendable for the reader to be passed into the closure; done means reaching a documented decision about their sendability and the affected API surface.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100