nros rmw-cffi
C vtable for plugging a third-party RMW backend into nros
Loading...
Searching...
No Matches
Data Fields
rmw_subscription_t Struct Reference

#include <rmw_entity.h>

Collaboration diagram for rmw_subscription_t:
Collaboration graph
[legend]

Data Fields

uint8_t _reserved [7]
 
void * backend_data
 
bool can_loan_messages
 
rmw_qos_profile_t qos
 
const char * topic_name
 
const char * type_name
 

Detailed Description

Subscription entity (phase-301: renamed from subscriber to the upstream rmw_subscription_t term). Same shape as the publisher; can_loan_messages means the backend exposes the receive-side loan primitive.

Field Documentation

◆ _reserved

uint8_t rmw_subscription_t::_reserved[7]

Reserved for future fields; must be zero.

◆ backend_data

void* rmw_subscription_t::backend_data

Opaque backend state. NULL if creation failed.

◆ can_loan_messages

bool rmw_subscription_t::can_loan_messages

Backend exposes loan_recv / release_recv (Phase 99). DERIVED by the runtime from vtable->take_loaned_message; a backend's write is overwritten (issue 0814).

◆ qos

rmw_qos_profile_t rmw_subscription_t::qos

QoS subset honoured by this subscription.

◆ topic_name

const char* rmw_subscription_t::topic_name

Topic name (borrowed; outlives the subscription).

◆ type_name

const char* rmw_subscription_t::type_name

Fully-qualified type name. Borrowed.


The documentation for this struct was generated from the following file: