Tracking Issue for macro_metavar_expr_concat
#124225
Labels
B-experimental
Feature: In-tree experiment; RFC pending or unneeded.
C-tracking-issue
Category: A tracking issue for an RFC or an unstable feature.
F-macro_metavar_expr_concat
`#![feature(macro_metavar_expr_concat)]`
I-lang-nominated
The issue / PR has been nominated for discussion during a lang team meeting.
S-tracking-unimplemented
Status: The feature has not been implemented.
T-lang
Relevant to the language team, which will review and decide on the PR/issue.
This is a tracking issue for the experimental feature macro metavariable expression
concat
(RFC pending).The feature gate for the issue is
#![feature(macro_metavar_expr_concat)]
.Provides a modern alternative to the
concat_idents!
macro.About experimental features
An experimental feature is one that has not yet had an RFC. The idea is to allow implementation work to proceed to better inform an upcoming RFC. Experimental features cannot be stabilized without first having an RFC. The existence of an experimental feature does not indicate lang team consensus that the feature is desirable, only that there is a problem that is worthy of being solved and that the idea has enough merit to consider exploring. See the lang team process page for more details.
About tracking issues
Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.
Steps / History
Unresolved Questions
References
The text was updated successfully, but these errors were encountered: