exonum_flamer 0.1.4

a procedural macro to insert `flame::start_guard(_)` calls

A plugin to insert appropriate flame::start_guard(_) calls (for use with flame)

Build Status Current Version Docs

This needs a nightly rustc! Because flamer is a compiler plugin, it uses unstable APIs, which are not available on stable or beta. It may be possible to extend flamer to allow use with syntex, but this hasn't been tried yet.


In your Cargo.toml add flame and flamer to your dependencies:

flame = "^0.1.9"
flamer = "^0.1.4"

Then in your crate root, add the following:

#![feature(plugin, custom_attribute)]

extern crate flame;

You may also opt for an optional dependency. In that case your Cargo.toml should have:

flame = { version = "^0.1.9", optional = true }
flamer = { version = "^0.1.4", optional = true }

default = []
flame_it = ["flame", "flamer"]

And your crate root should contain:

#![cfg_attr(feature="flame_it", feature(plugin, custom_attribute))]
#![cfg_attr(feature="flame_it", plugin(flamer))]

extern crate flame;

// as well as the following instead of `#[flame]`
#[cfg_attr(feature="flame_it", flame)];

You should then be able to annotate every item (or even the whole crate) with #[flame] annotations. You can also use #[noflame] annotations to disable instrumentations for subitems of #[flame]d items. Note that this only instruments the annotated methods, it does not print out the results.

Refer to flame's documentation to see how output works.

License: Apache 2.0