rust-lang / rust-lang/edition-guide
Explain why macros cannot be imported from the same crate
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 324
- Forks
- 152
- PR merge metrics
- No merged PRs in 30d
Description
I was reading the Macro Changes page:
Note that you'll still need
#[macro_use]to use macros you've defined in your own crate; this feature only works for importing macros from external crates.
A couple questions that immediately came to mind:
- Why? Could a link be added for people to read more about this?
- Is it planned that in the future you can import macros from your own crate?
I think it would be helpful to add a little background about this, as I'm sure others will have similar questions.
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 Macro Changes page linked in the issue and inspect its source in the edition-guide repository. Add concise background explaining why same-crate macros still require #[macro_use], include a link for further reading, and address whether future support is planned; the page should answer both questions clearly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100