Hi, I have tried my hand at a macro that should wrap slog macro calls to make it easier to have consistent messages. I can use this macro like this: gen_log_error!(1010, "Things are {how} bad"); Which generates a mcro called log_error_1010. I have one issue and one question: Issue Whenever I …

[image] Proc macros - using third party crate help The Rust solution to this, more general than just to procedural macros, are public dependencies through public reexports: //! Your `lib.rs` // 2018 edition pub use ::itertools; // old style pub extern crate itertools; a…

You need to re-export slog in your crate using: pub use slog; Then your macro can emit imports into your crate like ::your_crate::slog::foo_bar.

When you say your crate which one do you mean? The proc-macro crate or the "customer" using the crate? I tried it before in the proc-macro crate but I get this error: error: `proc-macro` crate types currently cannot export any items other than functions tagged with `#[proc_macro]`, `#[proc_macro_…

Right.. Usually you have a non-proc-macro crate that users import, which re-exports the proc-macro along with any dependencies the proc-macro needs. See @Yandros ' post for more details.

@alice & @Yandros Thank you very much. I got it working using your solution.

Problem with dependencies in Macros

help

Yandros September 15, 2020, 10:31am 3

Topic		Replies	Views
Log macro not found in library help	7	2482	August 21, 2016
How to export a macro that relies on third party crate help	2	671	January 9, 2025
Why should simplelog's dependencies be introduced when its paris feature is enabled? help	1	957	March 5, 2022
Proc macros - using third party crate help	3	5881	May 12, 2020
Creating libraries with somewhat-hygenic procedural macros to avoid dependency explosions? help	6	458	May 9, 2022

Problem with dependencies in Macros

Related topics