# THIS FILE IS AUTOMATICALLY GENERATED BY CARGO
#
# When uploading crates to the registry Cargo will automatically
# "normalize" Cargo.toml files for maximal compatibility
# with all versions of Cargo and also rewrite `path` dependencies
# to registry (e.g., crates.io) dependencies
#
# If you believe there's an error in this file please file an
# issue against the rust-lang/cargo repository. If you're
# editing this file be aware that the upstream Cargo.toml
# will likely look very different (and much more reasonable)

[package]
edition = "2018"
name = "tracers-macros-hack"
version = "0.1.0"
authors = ["Adam Nelson <anelson@127.io>"]
description = "Do not reference this crate directly; see the \"tracers\" crate for further instructions.\n\nThis crate contains the actual `proc-macro=true` crate which implements the probing macros.  Because the\n`probe!` macro is actually a procedural macro but is used in expression position, we must use the `proc_macro_hack` crate\nto work around the fact that Rust doesn't natively support this usage yet.  That hack requires that the actual macro be implemented\nin one crate, then re-exported from a second crate.  Thus, to ensure that callers can simply add a dependency on `tracers_macros`,\nwe make `tracers_macros` the re-exporting crate and this one, `tracers_macros_hack`, the actual proc macro crate.\n\nConfused?  Me too.\n"
license = "MIT OR Apache-2.0"
repository = "https://github.com/anelson/tracers"

[lib]
proc-macro = true
[dependencies.failure]
version = "0.1.6"

[dependencies.heck]
version = "0.3.1"

[dependencies.once_cell]
version = "1.2.0"

[dependencies.proc-macro-hack]
version = "0.5.11"

[dependencies.proc-macro2]
version = "1.0.6"

[dependencies.quote]
version = "1.0.2"

[dependencies.syn]
version = "1.0.8"
features = ["full"]

[dependencies.tracers-codegen]
version = "0.1.0"

[dependencies.tracers-core]
version = "0.1.0"
[dev-dependencies.quickcheck]
version = "0.9.0"

[dev-dependencies.quickcheck_macros]
version = "0.8.0"