dewit 0.0.1

Define scheduling and execution of code separately from data flow
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52

use crate::{
    mode::Mode,
    task::{Task, TaskOutput},
};

struct Join<A, B> {
    a: A,
    b: B,
}

impl<'src, AI, BI, AO, BO, A, B> Task<'src, (AI, BI), (AO, BO)> for Join<A, B>
where
    AI: Send + 'src,
    BI: Send + 'src,
    AO: Send + 'src,
    BO: Send + 'src,
    A: Task<'src, AI, AO> + Send + 'src,
    B: Task<'src, BI, BO> + Send + 'src,
{
    go_impl!('src, (AI, BI), (AO, BO));

    #[inline]
    fn go<M>(self, mode: &'src M, input: (AI, BI)) -> TaskOutput<'src, M, (AO, BO)>
    where
        Self: Sized,
        M: Mode<'src> + Send + Sync,
    {
        mode.join(
            move |mode| self.a.go(mode, input.0),
            move |mode| self.b.go(mode, input.1),
        )
    }
}

/// Combine two tasks by feeding the output of one into the next.
///
/// For ergonomics, [`Task::then`] should be preferred, but until `const` trait
/// functions are stabilized this function permits _constructing_ a [`Task`] to
/// be evaluated at compile time.
#[inline(always)]
pub const fn join<'src, AI, BI, AO, BO>(
    a: impl Task<'src, AI, AO> + Send + 'src,
    b: impl Task<'src, BI, BO> + Send + 'src,
) -> impl Task<'src, (AI, BI), (AO, BO)>
where
    AI: Send + 'src,
    BI: Send + 'src,
    AO: Send + 'src,
    BO: Send + 'src,
{
    Join { a, b }
}