phoxal 0.64.0

Phoxal - production-oriented autonomous robot framework: the runtime engine and model (the api contract tree lives in phoxal-protocol, the typed bus in phoxal-bus).
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
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92

//! The sealed capability surface a role attribute grants a participant marker.
//!
//! Each trait here is a capability token, not behavior: implementing it is what
//! makes a group of [`SetupContext`](crate::SetupContext) methods, or a
//! scheduled step, exist for one marker type. The role attribute is the only
//! implementor, so the set of capabilities a participant has is fixed by which
//! attribute authored it and cannot be widened from the participant's own
//! crate.
//!
//! [`sealing::Sealed`] is what enforces that: both traits require it, and only
//! macro-generated code inside a participant crate can name it, so an author
//! cannot hand-write `impl ComponentBoundSurface for MyService` to reach a
//! component binding it was not launched for.
//!
//! There is no schedulable marker any more: every remaining role - service,
//! driver, brain - owns a step, so a marker gating one would be satisfied by
//! every participant that can exist. It existed to keep the deleted simulator
//! role out of the scheduler, and it went with that role.

/// The sealing boundary for macro-emitted setup capabilities.
#[doc(hidden)]
pub mod sealing {
    pub trait Sealed {}
}

/// Typed bus IO: publishers, subscribers, queriers, and query registration.
#[doc(hidden)]
pub trait TypedIoSurface: sealing::Sealed {}

/// A bound `robot.components` entry, readable through
/// [`SetupContext::component`](crate::SetupContext::component).
#[doc(hidden)]
pub trait ComponentBoundSurface: sealing::Sealed {}

#[cfg(test)]
mod tests {
    use super::{ComponentBoundSurface, TypedIoSurface};
    use crate::participant::spec::ParticipantSpec;
    use crate::prelude::*;
    use phoxal_runtime_contract::metadata::ParticipantKind;

    #[phoxal::driver(id = "marker-driver")]
    struct MarkerDriver;

    impl Participant for MarkerDriver {
        async fn setup(
            &self,
            _ctx: &mut SetupContext<Self>,
            _config: Self::Config,
        ) -> Result<(Self::State, Self::Api)> {
            Ok(((), ()))
        }
    }

    #[phoxal::brain]
    struct MarkerBrain;

    impl Participant for MarkerBrain {
        async fn setup(
            &self,
            _ctx: &mut SetupContext<Self>,
            _config: Self::Config,
        ) -> Result<(Self::State, Self::Api)> {
            Ok(((), ()))
        }
    }

    /// Each kind macro emits its own marker, which is what gates the
    /// kind-specific `SetupContext` accessors.
    #[test]
    fn kind_macros_emit_their_markers() {
        fn assert_driver<T: ComponentBoundSurface + TypedIoSurface>() {}

        assert_driver::<MarkerDriver>();
    }

    /// The brain is a checked participant and nothing more: typed I/O and a
    /// step, never a component binding. The negative half is a trybuild case
    /// (`brain_has_no_privileged_capabilities`), since an unimplemented trait
    /// cannot be asserted from inside the crate that defines it.
    #[test]
    fn the_brain_marker_is_checked_only() {
        fn assert_checked<T: TypedIoSurface>() {}

        assert_checked::<MarkerBrain>();
        assert_eq!(<MarkerBrain as ParticipantSpec>::ID, "brain");
        assert_eq!(
            <MarkerBrain as ParticipantSpec>::KIND,
            ParticipantKind::Brain
        );
    }
}