Struct riot_wrappers::msg::v2::NoConfiguredMessages

pub struct NoConfiguredMessages;

Available on riot_module_core_msg and crate feature with_msg_v2 only.

Implementations

impl NoConfiguredMessages

The MessageSemantics of a thread that has made no previous commitment to receive any messages.

pub(crate) unsafe fn new() -> Self

Create a new MessageSemantics object to split into ReceivePorts.

Conditions, violating which is a safety violation:

• The thread must currently not allow sending any messages to it, or even created an otherwise unused NoConfiguredMessages

• The thread must not terminate.

TBD: Add a version of the thread spawner that comes with all kinds of once-per-thread gadgets.

Trait Implementations

impl MessageSemantics for NoConfiguredMessages

unsafe fn drop(_message: &mut ReceivedMessage<'_, Self>)

Panicking because if a thread receives unknown messages, it may for the same reason receive mistyped messages, and that’d be a safety violation that’s better shown in the most visible way.

If this is undesired, think twice about whether the source of the message really can’t happen to send messages of a number this threads expects (and handles as something different) as well. If it is still undesired, you can core::mem::forget() the message after having decoded all desired types.

fn typeno_is_known(&self, _typeno: u16) -> bool

fn split_off<NewType: Send, const NEW_TYPENO: u16>( self, ) -> (Processing<Self, NewType, NEW_TYPENO>, ReceivePort<NewType, NEW_TYPENO>, SendPort<NewType, NEW_TYPENO>)

Reduce the type into a new MessageSemantics that knows about one more typeno, and a ReceivePort that can be used to create a SendPort or to process incoming messages.

fn receive(&self) -> ReceivedMessage<'_, Self>

Block to receive a single message

fn try_receive(&self) -> Option<ReceivedMessage<'_, Self>>

Receive a single message if one is available in the queue (or another thread is blocking to send a message, if no queue is used)

Layout

Note: Most layout information is completely unstable and may even differ between compilations. The only exception is types with certain repr(...) attributes. Please see the Rust Reference's “Type Layout” chapter for details on type layout guarantees.

Size: 0 bytes