actor.h File Reference

Deterministic runtime actor composition. More...

#include <cstddef>
#include <tuple>
#include <type_traits>
#include <utility>
#include "tsm/runtime/concepts.h"
#include "tsm/runtime/resources.h"

Include dependency graph for actor.h:

This graph shows which files directly or indirectly include this file:

Go to the source code of this file.

Classes
struct	tsm::runtime::input_port< Event, Sink >
struct	tsm::runtime::output_port< Event, Source >
struct	tsm::runtime::actor_link< Source, Sink >
struct	tsm::runtime::actor_group< Actors >
struct	tsm::runtime::actor_resources< Actor >
struct	tsm::runtime::actor_group_resources< Actors >
	Aggregate resource summaries for several actor types. More...

Namespaces
	tsm
	tsm::runtime
	tsm::runtime::detail

Functions
template<typename Event , typename Sink >
constexpr input_port< Event, Sink >	tsm::runtime::make_input_port (Sink &sink)
template<typename Event , typename Source >
constexpr output_port< Event, Source >	tsm::runtime::make_output_port (Source &source)
template<typename Source , typename Sink >
	tsm::runtime::actor_link (Source &, Sink &) -> actor_link< Source, Sink >
template<typename... Links>
bool	tsm::runtime::link_all (Links &... links)
template<typename... Actors>
	tsm::runtime::actor_group (Actors &...) -> actor_group< Actors... >
consteval resource_snapshot	tsm::runtime::detail::add_resource_snapshots (resource_snapshot lhs, resource_snapshot rhs)

Variables
template<typename Actor >
concept	tsm::runtime::actor_like
template<typename Actor , typename Event >
concept	tsm::runtime::actor_sink
template<typename Actor , typename Event >
concept	tsm::runtime::actor_source
template<typename Source , typename Sink >
concept	tsm::runtime::compatible_link

Detailed Description

Deterministic runtime actor composition.

Actors are the runtime composition unit for systems built from several bounded components. An actor may be an HSM runtime, a sensor adapter, a replay source, a reporting sink, or a small product-specific handler. The actor layer only defines typed ingress/egress, deterministic stepping, and resource aggregation; it does not own threads, callbacks, discovery, or domain vocabulary.