When code needs to work with asciichat errno snapshot, it keeps total, copied here instead of scattering it across globals. Initialization establishes the handles and sizes; teardown must release any allocation, lock, thread, or callback context recorded in those fields. More...

#include <include/ascii-chat/asciichat_errno.h>

Data Fields
uint64_t	thread_id
uint64_t	generation
uint64_t	after_id
uint64_t	previous_after_id

Detailed Description

When code needs to work with asciichat errno snapshot, it keeps total, copied here instead of scattering it across globals. Initialization establishes the handles and sizes; teardown must release any allocation, lock, thread, or callback context recorded in those fields.

Checkpoints use IDs, not depths, so concurrent removals cannot invalidate them.

The useful part of asciichat errno scope is in thread_id, generation, after_id, previous_after_id: together they describe what is pending, who owns it, and how much data is valid. Keep the object with its parent operation and use the parent cleanup path.

Definition at line 90 of file asciichat_errno.h.