alloc_observe.Event

1/// An `Event` is a by-value notification delivered at span finish. This2/// notification conveys caller-supplied data rather than proof of actual3/// storage. Numeric addresses are diagnostic, providing no ownership,4/// capability, or dereference guarantee after an allocation expires. Ordinary5/// spans set lifecycle tags to none.6///7/// The exact fields and their meanings are:8///9/// - `operation_id`: operation identifier assigned at begin.10/// - `parent_operation_id`: identifier of the enclosing span or context on the11///   current thread, or zero if none exists.12/// - `producer_id`: numeric identifier of the producer.13/// - `producer`: kind of producer.14/// - `generation`: owner-supplied lifetime number.15/// - `owner_cookie`: owner association value.16/// - `operation`: executed allocation or lifecycle operation.17/// - `lifecycle_disposition`: lifecycle disposition tag, set to none for18///   ordinary spans.19/// - `lifecycle_reason`: lifecycle reason tag, set to none for ordinary spans.20/// - `address`: result address supplied to finish.21/// - `old_address`: prior address before the operation.22/// - `len`: requested or new length.23/// - `old_len`: prior length before the operation.24/// - `alignment`: alignment in bytes.25/// - `return_address`: caller instruction address.26/// - `succeeded`: producer result flag indicating success or failure.27///28/// When `beginLifecycle` opens a span, it sets old_address, old_len, and len to29/// zero, and alignment to one byte. That initialization does not dictate the30/// final result address supplied to finish. Nested spans on the same thread31/// deliver inner spans before outer spans, so operation identifiers do not32/// increase in delivery order. Concurrent callbacks have no globally serialized33/// order across threads. A silent context reserves an operation identifier but34/// emits no event, so a parent operation identifier can lack a matching event.35pub const Event = struct {36    operation_id: u64,37    parent_operation_id: u64,38    producer_id: u64,39    producer: Producer,40    generation: u64,41    owner_cookie: usize,42    operation: Operation,43    lifecycle_disposition: LifecycleDisposition,44    lifecycle_reason: LifecycleReason,45    address: usize,46    old_address: usize,47    len: usize,48    old_len: usize,49    alignment: usize,50    return_address: usize,51    succeeded: bool,52};

1/// An `Event` is a by-value notification delivered at span finish. This2/// notification conveys caller-supplied data rather than proof of actual3/// storage. Numeric addresses are diagnostic, providing no ownership,4/// capability, or dereference guarantee after an allocation expires. Ordinary5/// spans set lifecycle tags to none.6///7/// The exact fields and their meanings are:8///9/// - `operation_id`: operation identifier assigned at begin.10/// - `parent_operation_id`: identifier of the enclosing span or context on the11///   current thread, or zero if none exists.12/// - `producer_id`: numeric identifier of the producer.13/// - `producer`: kind of producer.14/// - `generation`: owner-supplied lifetime number.15/// - `owner_cookie`: owner association value.16/// - `operation`: executed allocation or lifecycle operation.17/// - `lifecycle_disposition`: lifecycle disposition tag, set to none for18///   ordinary spans.19/// - `lifecycle_reason`: lifecycle reason tag, set to none for ordinary spans.20/// - `address`: result address supplied to finish.21/// - `old_address`: prior address before the operation.22/// - `len`: requested or new length.23/// - `old_len`: prior length before the operation.24/// - `alignment`: alignment in bytes.25/// - `return_address`: caller instruction address.26/// - `succeeded`: producer result flag indicating success or failure.27///28/// When `beginLifecycle` opens a span, it sets old_address, old_len, and len to29/// zero, and alignment to one byte. That initialization does not dictate the30/// final result address supplied to finish. Nested spans on the same thread31/// deliver inner spans before outer spans, so operation identifiers do not32/// increase in delivery order. Concurrent callbacks have no globally serialized33/// order across threads. A silent context reserves an operation identifier but34/// emits no event, so a parent operation identifier can lack a matching event.35pub const Event = protocol.Event;