Struct CallerInbox 

pub struct CallerInbox { /* private fields */ }

The header a caller hands the backend: a ring’s geometry and where its bytes are.

#[repr(C)] and four plain words, because this is the shape an ABI slot has to carry. The road from nros-node to the zenoh shim runs through nros-rmw-cffi’s C vtable (packages/core/nros-rmw-abi/include/nros/), which today has no create_service variant that takes one; until it does, crate::Session::SUPPORTS_CALLER_INBOX is false on every backend the runtime can reach and a family’s ServiceInboxSpec resolves to ServiceInboxSpec::Backend. Laying this out as an ABI struct now is what keeps that a forwarding problem rather than a redesign.

Implementations

impl CallerInbox

pub const fn over<const S: usize, const D: usize>( storage: &'static CallerInboxStorage<S, D>, ) -> Self

A header over storage the caller owns for the life of the program.

const, so a family writes static INBOX: CallerInbox = CallerInbox::over(&STORAGE); and hands the reference to ServiceInboxSpec::Caller.

pub const fn slot_bytes(&self) -> usize

Bytes one request slot holds.

pub const fn depth(&self) -> usize

Slots in the ring.

pub const fn storage_bytes(&self) -> usize

Bytes this ring’s storage occupies (slots and entries).

pub fn is_over<const S: usize, const D: usize>( &self, storage: &'static CallerInboxStorage<S, D>, ) -> bool

Does this header sit over storage? For tests, which need to say “the bytes landed in the caller’s static” rather than infer it.

Trait Implementations

impl Clone for CallerInbox

fn clone(&self) -> CallerInbox

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Copy for CallerInbox

impl Send for CallerInbox

impl Sync for CallerInbox