File tree Expand file tree Collapse file tree 1 file changed +0
-22
lines changed Expand file tree Collapse file tree 1 file changed +0
-22
lines changed Original file line number Diff line number Diff line change 2
2
- given that the point of `reader` is to *allow* (cancelable) I/O, this occurs too often to be practical
3
3
-> remove it?
4
4
- move `background`/`Worker` etc. into a `thread` module
5
- - "isochronous" stream processing that replicates the input data pacing at the output while running
6
- the computation pipelined on a thread pool
7
5
- add a hybrid channel similar to flume (except without the dependencies)
8
6
9
- reactive value sketch
10
-
11
- impl Value<T> {
12
- pub fn new() -> Self { ... }
13
-
14
- pub fn set(&self, value: T) { ... }
15
-
16
- pub fn reader(&self) -> Reader<T> { ... }
17
- pub fn reader_count(&self) -> usize { ... }
18
- }
19
-
20
- impl Reader<T> {
21
- pub fn get(&self) -> Option<T> { ... }
22
- pub fn next(&self) -> Option<T> { ... }
23
-
24
- pub async fn wait(&self) -> T { ... }
25
- pub fn block(&self) -> T { ... }
26
- }
27
-
28
-
29
7
isochronous processor might be better as a `Stream` extension (`stream.pace()`?)
30
8
a better name relating to "wall clock time" might also be better
You can’t perform that action at this time.
0 commit comments