async-rs / async-rs/stop-token

figure out how to work with temporal streams too

Open
#14 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
50
Forks
7
PR merge metrics
No merged PRs in 30d

Description

![Screenshot_20220108-235531](https://user-images.githubusercontent.com/2467194/148662607-b783c496-c91f-4d42-b72d-014488c1d1d9.png)

![Screenshot_20220108-235822](https://user-images.githubusercontent.com/2467194/148662674-6fc53f89-aeea-433f-9203-d713f73fd7f7.png)

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue contains only two screenshots and does not name a file, test, entry point, or specific behavior to change. Start by inspecting the stop-token repository and the screenshots to determine what temporal streams require; the expected behavior and a testable definition of done still need clarification.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
stream-processing
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.