fn generate_probe_doc_comment(&self, provider: &ProviderSpecification) -> TokenStream {
        let probe_comment = format!(r###"
# Probing

This method is translated at compile-time by `tracers` into a platform-specific tracing
probe, which allows very high-performance and low-overhead tracing.

## How to fire probe

To fire this probe, don't call this method directly. Instead, use the `probe!` macro, for example:

```ignore
// If the probe is enabled, fires the probe.  If the probe isn't enabled, or if provider
// initialization failed for some reason, does not fire the probe, and does NOT evaluate the
// arguments to the probe.
probe!({trait_name}::{probe_name}(...));
```

The exact details of how to interact with the probes depends on the underlying
probing implementation.

## SystemTap/USDT (Linux x64)

To trace the firing of this probe, use `bpftrace`, e.g.:
```text
sudo bpftrace -p ${{PID}} -e 'usdt::{provider}:{probe_name} {{ printf("Hello from {probe_name}\n"); }}'
```

where `${{PID}}` should be the actual process ID of the process you are tracing.

## Other platforms

TODO: No other platforms supported yet

"###,
        trait_name = &provider.item_trait().ident,
        probe_name = &self.spec().name,
        provider = provider.name(),
);

        generate_multiline_comments(&probe_comment)
    }
/// Generates a doc comment to attach to the probe's method.  This includes additional information
/// about how to work with this probe on various platforms.
Generates a doc comment to attach to the probe's method.  This includes additional information
about how to work with this probe on various platforms.
Generates a doc comment to attach to the probe ' s method . This includes additional information about how to work with this probe on various platforms .
fn generate_probe_doc_comment(&self, provider: &ProviderSpecification) -> TokenStream {
        let probe_comment = format!(r###"
# Probing
This method is translated at compile-time by `tracers` into a platform-specific tracing
probe, which allows very high-performance and low-overhead tracing.
## How to fire probe
To fire this probe, don't call this method directly. Instead, use the `probe!` macro, for example:
```ignore
// If the probe is enabled, fires the probe.  If the probe isn't enabled, or if provider
// initialization failed for some reason, does not fire the probe, and does NOT evaluate the
// arguments to the probe.
probe!({trait_name}::{probe_name}(...));
```
The exact details of how to interact with the probes depends on the underlying
probing implementation.
## SystemTap/USDT (Linux x64)
To trace the firing of this probe, use `bpftrace`, e.g.:
```text
sudo bpftrace -p ${{PID}} -e 'usdt::{provider}:{probe_name} {{ printf("Hello from {probe_name}\n"); }}'
```
where `${{PID}}` should be the actual process ID of the process you are tracing.
## Other platforms
TODO: No other platforms supported yet
"###,
        trait_name = &provider.item_trait().ident,
        probe_name = &self.spec().name,
        provider = provider.name(),
);
        generate_multiline_comments(&probe_comment)
    }
fn generate_probe_doc_comment ( & self , provider : & ProviderSpecification ) -> TokenStream { let probe_comment = format ! ( r###"
# Probing

This method is translated at compile-time by `tracers` into a platform-specific tracing
probe, which allows very high-performance and low-overhead tracing.

## How to fire probe

To fire this probe, don't call this method directly. Instead, use the `probe!` macro, for example:

```ignore
// If the probe is enabled, fires the probe.  If the probe isn't enabled, or if provider
// initialization failed for some reason, does not fire the probe, and does NOT evaluate the
// arguments to the probe.
probe!({trait_name}::{probe_name}(...));
```

The exact details of how to interact with the probes depends on the underlying
probing implementation.

## SystemTap/USDT (Linux x64)

To trace the firing of this probe, use `bpftrace`, e.g.:
```text
sudo bpftrace -p ${{PID}} -e 'usdt::{provider}:{probe_name} {{ printf("Hello from {probe_name}\n"); }}'
```

where `${{PID}}` should be the actual process ID of the process you are tracing.

## Other platforms

TODO: No other platforms supported yet

"### trait_name provider item_trait ( ) ident probe_name self spec ( ) name provider provider name ( ) ) ; generate_multiline_comments ( & probe_comment ) }
Generates a doc comment to attach to the probe's method.
Generates a doc comment to attach to the probe ' s method .
&self
provider
&ProviderSpecification
&self
provider
&ProviderSpecification