-
-
Notifications
You must be signed in to change notification settings - Fork 16.1k
Built-in derive macros Encodable, Decodable, RustcEncodable and RustcDecodable are stable #62048
Copy link
Copy link
Closed
Labels
A-macrosArea: All kinds of macros (custom derive, macro_rules!, proc macros, ..)Area: All kinds of macros (custom derive, macro_rules!, proc macros, ..)A-stabilityArea: `#[stable]`, `#[unstable]` etc.Area: `#[stable]`, `#[unstable]` etc.C-bugCategory: This is a bug.Category: This is a bug.P-mediumMedium priorityMedium priorityT-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.
Description
Activity
Metadata
Metadata
Assignees
Labels
A-macrosArea: All kinds of macros (custom derive, macro_rules!, proc macros, ..)Area: All kinds of macros (custom derive, macro_rules!, proc macros, ..)A-stabilityArea: `#[stable]`, `#[unstable]` etc.Area: `#[stable]`, `#[unstable]` etc.C-bugCategory: This is a bug.Category: This is a bug.P-mediumMedium priorityMedium priorityT-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.
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.