The macros produce paths like serialize::foo or rustc_serialize::foo and I suspect that the feature gating was supposed to happen when you write extern crate serialize to bring that serialize into scope.
However, you can easily write use anything as serialize, and rustc_serialize is a stable crate on crates.io, so this kind of feature gating doesn't work.
After #62042 lands we should try to un-stabilize them and test it with crater.
The macros produce paths like
serialize::fooorrustc_serialize::fooand I suspect that the feature gating was supposed to happen when you writeextern crate serializeto bring thatserializeinto scope.However, you can easily write
use anything as serialize, andrustc_serializeis a stable crate on crates.io, so this kind of feature gating doesn't work.After #62042 lands we should try to un-stabilize them and test it with crater.