Allow macros to be used in literals and/or meta items
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 6.6k
- Forks
- 1.7k
- Avg merge
- 16h 14m
- Merged PRs (30d)
- 1
Description
In this reddit comment Perceptes mentioned one idea to cut down down on some of the syntex boilerplate would be to use the #[path = ...] attribute to point to one of the generated files, as in this:
#[path = concat!(env!("OUT_DIR"), "/generated_foo.rs")]
mod foo;
Unfortunately this is currently illegal, because macros cannot be used in the position of a literal. It would be nice if we supported this functionality.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the issue's Rust example using #[path = concat!(env!("OUT_DIR"), "/generated_foo.rs")], and investigate the rules that reject macros in literal or meta-item positions. Done means the proposed macro usage is supported, with the relevant behavior defined and validated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100