You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using Rust 1.30 it is possible to bring macros into scope using use instead of #[macro_use]. I am therefore (perhaps a bit over-zealously) trying to get rid of all instances of #[macro_use] in my crates, when I hit upon what seems to be a strange edge case regarding the following bit of code:
ron enables serde's serde_derive feature which reexports the derive macros. If you stop depending on ron, that feature stops being activated. You can either directly depend on the serde_derive crate or enable the feature yourself: https://docs.rs/crate/ron/0.4.0/source/Cargo.toml.orig.
Aaah, I see! I had never realized before that a dependant crate could modify which features I can use from another crate. So this is not a bug. Sorry for the noise and thank you very much for the explanation!
Using Rust 1.30 it is possible to bring macros into scope using
use
instead of#[macro_use]
. I am therefore (perhaps a bit over-zealously) trying to get rid of all instances of#[macro_use]
in my crates, when I hit upon what seems to be a strange edge case regarding the following bit of code:Using the following
Cargo.toml
, which includes a dependency onron
which is not used in the code:This compiles fine:
However when I remove the dependency on
ron
(which itself depends onserde
) from myCargo.toml
:Then I get a compile error:
Meta
The text was updated successfully, but these errors were encountered: