-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Deprecate the unstable concat_idents!
#137653
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.
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
base: master
Are you sure you want to change the base?
Conversation
r? @nnethercote rustbot has assigned @nnethercote. Use |
r? libs-api |
concat_idents!
concat_idents!
ecac1cc
to
4f7ea23
Compare
I'd like to propose deprecating it now (1.87) and removing in the next version (1.88), nominating for libs-api. Cc @rust-lang/lang since this is tightly coupled. |
Let's just FCP it. That's maybe weird for an unstable thing, but no more weird than doing a deprecation cycle for it. @rfcbot fcp merge |
Team member @traviscross has proposed to merge this. The next step is review by the rest of the tagged team members: No concerns currently listed. Once a majority of reviewers approve (and at most 2 approvals are outstanding), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up! cc @rust-lang/lang-advisors: FCP proposed for lang, please feel free to register concerns. |
@rfcbot reviewed |
👍 for deprecating I saw that @tgross35 proposed rust-lang/rfcs#3649 to supersede the |
That's correct; I think |
@rustbot labels -I-lang-nominated We discussed this in the lang call today. Thanks @tgross35 for pushing this forward. As above, the one question that came up was whether this was related to our open question: But it's not, as |
🔔 This is now entering its final comment period, as per the review above. 🔔 |
The final comment period, with a disposition to merge, as per the review above, is now complete. As the automated representative of the governance process, I would like to thank the author for their work and everyone else who contributed. This will be merged soon. |
Is there a plan for if/when this feature will go from deprecated to removed? |
From earlier in this thread:
|
I wasn't sure if that "removing in the next version" was part of the approved FCP or just the PR contents itself. But if the FCP also included the removing, then that's cool with me |
4f7ea23
to
71beeb0
Compare
Rebased, FCP completed so this just needs a review. @rustbot ready |
71beeb0
to
fde9fcb
Compare
Since fcp is complete I'll roll for libs r? libs |
Cool, thanks! @bors r+ rollup |
Note that this has slipped to 1.88, and I suppose removal in 1.89, unless we also beta-backport the deprecation. |
Ah good catch, let me update that. It would be nice if deprecated supported |
fde9fcb
to
3f7d833
Compare
`concat_idents` has been around unstably for a long time, but there is now a better (but still unstable) way to join identifiers using `${concat(...)}` syntax with `macro_metavar_expr_concat`. This resolves a lot of the problems with `concat_idents` and is on a better track toward stabilization, so there is no need to keep both versions around. `concat_idents!` still has a lot of use in the ecosystem so deprecate it before removing, as discussed in [1]. Link: rust-lang#124225 [1]: https://rust-lang.zulipchat.com/#narrow/channel/219381-t-libs/topic/Removing.20.60concat_idents.60
3f7d833
to
75a9be6
Compare
@bors r=workingjubilee |
Hmm, I think that should work -- the tool simply calls
(although the placeholder is |
I did try it before and IIRC it got rejected somewhere for not being a valid version. But maybe I just made the same typo at that time too :) |
Oh, I didn't think about attribute validation -- you're right, it doesn't work, and it should! |
concat_idents
has been around unstably for a long time, but there is now a better (but still unstable) way to join identifiers using${concat(...)}
syntax withmacro_metavar_expr_concat
. This resolves a lot of the problems withconcat_idents
and is on a better track toward stabilization, so there is no need to keep both versions around.concat_idents!
still has a lot of use in the ecosystem so deprecate it before removing, as discussed in 1.Link: #124225