-
Notifications
You must be signed in to change notification settings - Fork 13.4k
rustc: Stabilize the proc_macro
feature
#38783
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Conversation
This commit stabilizes the `proc_macro` and `proc_macro_lib` features in the compiler to stabilize the "Macros 1.1" feature of the language. Many more details can be found on the tracking issue, rust-lang#35900. Closes rust-lang#35900
r? @aturon (rust_highfive has picked a reviewer for you, use r? to override) |
🎊🎉 |
|
@bors r+ |
@bors r- |
@abonander raises a good point! :) @alexcrichton, are there other users of |
@abonander to clarify, is that implemented? I couldn't find @nikomatsakis AFAIK nothing else is, no |
I've started tinkering on it because I'd like to experiment with the feature. It actually looks pretty straightforward, mostly just copying custom derive. |
@abonander I'm still a little confused? I haven't been following all the proc-macro business that closely. What is |
It is not currently supported in the compiler, though the pieces are (mostly) there. I'd have to read over the RFC again but I don't think it uses its own feature flag, though that can be changed trivially. |
Ok, sounds like that can just have a new feature gate if it isn't already implemented? I'm sort of confused, does this PR need to change? |
I don't think so, we just need to make sure the feature gate for the other two proc macro kinds is different. |
@bors r+ p=1 |
📌 Commit 045f8f6 has been approved by |
Marking as beta-accepted. The whole point is to backport this -- and anyway it's 99% marking stuff stable. cc @rust-lang/compiler |
☀️ Test successful - status-appveyor, status-travis |
This commit stabilizes the
proc_macro
andproc_macro_lib
features in thecompiler to stabilize the "Macros 1.1" feature of the language. Many more
details can be found on the tracking issue, #35900.
Closes #35900