Skip to content

Tracking issue for dual-proc-macros #64671

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
ehuss opened this issue Sep 21, 2019 · 4 comments
Open

Tracking issue for dual-proc-macros #64671

ehuss opened this issue Sep 21, 2019 · 4 comments
Assignees
@petrochenkov
Labels
A-macros Area: All kinds of macros (custom derive, macro_rules!, proc macros, ..) A-proc-macros Area: Procedural macros B-unstable Blocker: Implemented in the nightly compiler and unstable. C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC requires-nightly This issue requires a nightly compiler in some way. S-tracking-design-concerns Status: There are blocking design concerns. S-tracking-needs-summary Status: It's hard to tell what's been done and what hasn't! Someone should do some investigation. S-tracking-perma-unstable Status: The feature will stay unstable indefinitely. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.

Comments

@ehuss
Copy link
Contributor

ehuss commented Sep 21, 2019

Implemented in #58013
Cargo side is rust-lang/cargo#6547

This feature causes Cargo to build a proc-macro crate for both the target and the host, and for rustc to load both.

I'm not sure if this is a perma-unstable feature for the compiler-only, or if there is any need to use it elsewhere. But a tracking issue may be helpful for anyone looking for more information.
@ehuss ehuss added the C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC label Sep 21, 2019
@ehuss ehuss mentioned this issue Sep 21, 2019
Merged
@jonas-schievink jonas-schievink added A-macros Area: All kinds of macros (custom derive, macro_rules!, proc macros, ..) B-unstable Blocker: Implemented in the nightly compiler and unstable. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels Sep 21, 2019
@Centril Centril added the requires-nightly This issue requires a nightly compiler in some way. label Sep 23, 2019
@crlf0710
Copy link
Member

This might has something to do with #62558, according to the patches in termux/termux-packages#4324 (comment)

@mati865
Copy link
Contributor

mati865 commented Oct 12, 2019

See also #62558 (comment)

@petrochenkov
Copy link
Contributor

Some more detailed explanation of why this feature is necessary and how it works - https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/-Z.20dual-proc-macros.

@petrochenkov petrochenkov self-assigned this Oct 16, 2019
@Aaron1011 Aaron1011 added the A-proc-macros Area: Procedural macros label May 21, 2020
@ehuss ehuss mentioned this issue Dec 22, 2020
Closed
@pnkfelix
Copy link
Member

Discussed in T-compiler backlog bonanza

Our understanding is that this is a fragile bit of code in here to support cross-compiling of rustc itself. We don't want to stabilize it as is. Its possible we want to try to get rid of it, depending on how one interprets the dialogue at #t-compiler > -Z dual-proc-macros

@rustbot label: S-tracking-design-concerns S-tracking-perma-unstable

@rustbot rustbot added S-tracking-design-concerns Status: There are blocking design concerns. S-tracking-perma-unstable Status: The feature will stay unstable indefinitely. labels Aug 12, 2022
@jieyouxu jieyouxu added the S-tracking-needs-summary Status: It's hard to tell what's been done and what hasn't! Someone should do some investigation. label Mar 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@petrochenkov petrochenkov

Labels
A-macros Area: All kinds of macros (custom derive, macro_rules!, proc macros, ..) A-proc-macros Area: Procedural macros B-unstable Blocker: Implemented in the nightly compiler and unstable. C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC requires-nightly This issue requires a nightly compiler in some way. S-tracking-design-concerns Status: There are blocking design concerns. S-tracking-needs-summary Status: It's hard to tell what's been done and what hasn't! Someone should do some investigation. S-tracking-perma-unstable Status: The feature will stay unstable indefinitely. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
10 participants
@ehuss @pnkfelix @crlf0710 @Centril @mati865 @Aaron1011 @jonas-schievink @petrochenkov @jieyouxu @rustbot