`RuntimeUpdaterStream` should have a `try_next` or some non-blocking `next`
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 489
- Forks
- 293
- Avg merge
- 18h 35m
- Merged PRs (30d)
- 3
Description
The examples given spawn this update stream in a separate thread, so it doesn't blokck, but sometimes (for operation sequencing) this may not make sense. It would be helpful to have a try_next() that returns Option or Result if there's no item. Async channels tend to return Result and then the Error enum can have variants representing NoItems and ChannelClosed.
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 RuntimeUpdaterStream and the examples that spawn this update stream, then inspect how its current next operation behaves. The work is done when a non-blocking operation is defined for the stream, including the no-item and channel-closed outcomes, with the Option-versus-Result behavior resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100