tracers-macros-hack 0.1.0

Do not reference this crate directly; see the "tracers" crate for further instructions. This crate contains the actual `proc-macro=true` crate which implements the probing macros. Because the `probe!` macro is actually a procedural macro but is used in expression position, we must use the `proc_macro_hack` crate to work around the fact that Rust doesn't natively support this usage yet. That hack requires that the actual macro be implemented in one crate, then re-exported from a second crate. Thus, to ensure that callers can simply add a dependency on `tracers_macros`, we make `tracers_macros` the re-exporting crate and this one, `tracers_macros_hack`, the actual proc macro crate. Confused? Me too.
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
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55

[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]
features = ["full"]
version = "1.0.8"

[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"

[lib]
proc-macro = true

[package]
authors = ["Adam Nelson <anelson@127.io>"]
description = """
Do not reference this crate directly; see the "tracers" crate for further instructions.

This crate contains the actual `proc-macro=true` crate which implements the probing macros.  Because the
`probe!` macro is actually a procedural macro but is used in expression position, we must use the `proc_macro_hack` crate
to work around the fact that Rust doesn't natively support this usage yet.  That hack requires that the actual macro be implemented
in one crate, then re-exported from a second crate.  Thus, to ensure that callers can simply add a dependency on `tracers_macros`,
we make `tracers_macros` the re-exporting crate and this one, `tracers_macros_hack`, the actual proc macro crate.

Confused?  Me too.
"""
edition = "2018"
license = "MIT OR Apache-2.0"
name = "tracers-macros-hack"
repository = "https://github.com/anelson/tracers"
version = "0.1.0"