Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign uprustc: Tweak expansion order of custom derive #36782
Conversation
rust-highfive
assigned
aturon
Sep 27, 2016
This comment has been minimized.
This comment has been minimized.
|
r? @aturon (rust_highfive has picked a reviewer for you, use r? to override) |
This comment has been minimized.
This comment has been minimized.
|
r? @nrc the problem: #35900 (comment) |
rust-highfive
assigned
nrc
and unassigned
aturon
Sep 27, 2016
This comment has been minimized.
This comment has been minimized.
|
While reviewing this it occurred to me that we should deprecate the old style custom derive sooner rather than later. It is unstable, so I don't think we should wait for macros 1.1 to stabilise. |
This comment has been minimized.
This comment has been minimized.
|
@bors: r+ |
This comment has been minimized.
This comment has been minimized.
|
|
nikomatsakis
referenced this pull request
Sep 27, 2016
Closed
Tracking issue for "Macros 1.1" (RFC #1681) #35900
This comment has been minimized.
This comment has been minimized.
bors
added a commit
that referenced
this pull request
Sep 28, 2016
This comment has been minimized.
This comment has been minimized.
|
|
This comment has been minimized.
This comment has been minimized.
|
@bors: retry On Tue, Sep 27, 2016 at 7:50 PM, bors notifications@github.com wrote:
|
alexcrichton commentedSep 27, 2016
This commit alters the expansion order of custom macros-1.1 style
#[derive]modes. Instead of left-to-right the expansion now happens in three categories,
each of which is internally left-to-right:
#[derive_Foo]) is expandedThis gives built in derive modes maximal knowledge about the struct that's being
expanded and also avoids pesky issues like exposing
#[structural_match]or#[rustc_copy_clone_marker].cc #35900