tracers-codegen 0.1.0

Contains the compile-time code generation logic which powers the `probe` and `tracers` macros. Do not use this crate directly; see "tracers" for more information.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30

//! This module and its sub-modules contain structures which represent the parsed and processed
//! contents of the various probing macros, like `#[tracer]` and `probe!`.
//!
//! Though there are multiple different probing implementations supported, the way the programmer
//! specifies providers and the way probes are fired must be the same regardless of implementation.
//! Thus, the implementatino doesn't control how to the `TokenStream` is intepreted; the proc
//! macros first call into these modules to parse the input `TokenStream` into a specification of
//! what the programmer wants, complete with helpful error messages if the specification is invalid
//! in some way.
//!
//! Only once a validated specification is available can the code generators go to work.
//!
//! Thus this can be seen as one side of the code generator implementation.  The other side, which
//! actually generates probing code, is in the `gen` module.
mod init_provider;
mod probe;
mod probe_arg;
mod probe_call;
mod provider;

pub(crate) use init_provider::ProviderInitSpecification;
pub(crate) use probe::ProbeSpecification;
pub(crate) use probe_arg::ProbeArgSpecification;
#[cfg(test)]
pub(crate) use probe_call::ProbeCallDetails;
pub(crate) use probe_call::ProbeCallSpecification;
#[cfg(test)]
pub(crate) use provider::TracerAttribute;
pub(crate) use provider::TracerAttributeArgs;
pub(crate) use provider::{find_providers, ProviderSpecification};