-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Clean up the macros chapter #14058
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
Comments
/cc @aturon |
@steveklabnik Do you plan to write docs for writing macros? Our current docs there are very sparse. If/when you do that, I'd be glad to discuss terminology, though I'm a total novice. |
Yes, eventually, the macro guide is being completely redone. |
/cc @kmcallister , what's your opinion here? |
The macros chapter could use a lot of work. I think we should find more exciting examples for everything before "Hygiene" and then rewrite the explanation around those. I can take a shot at this before 1.0-final. |
In progress as #22393. |
Landed! ^_^ |
fix negative trait bound in outline view (rust-lang#14044) try to fix and close rust-lang#14044
It would be nice to use consistent terminology for macros.
For example, in
$a:b
, Macros Guide callsb
a "fragment specifier", Reference Manual calls it a "designator". Both are inscrutable, and looking at search engine hits "fragment specifier" seems to be a Rust coinage.Dylan calls it "constraint", which seems reasonable to me. See a section on Dylan Macro System documentation.
The text was updated successfully, but these errors were encountered: