Skip to content

Conversation

@iopq
Copy link
Owner

@iopq iopq commented Mar 2, 2017

d

Diggsey and others added 30 commits July 17, 2016 18:33
Extract a very small sliver of today's procedural macro system in the compiler,
just enough to get basic features like custom derive working, to have an
eventually stable API. Ensure that these features will not pose a maintenance
burden on the compiler but also don't try to provide enough features for the
"perfect macro system" at the same time. Overall, this should be considered an
incremental step towards an official "plugins 2.0".
Explicit type punning alternative.
steveklabnik and others added 29 commits January 5, 2017 20:07
Fix links & reveal hidden information
Macros by example 2.0. A replacement for `macro_rules!`. This is mostly a
placeholder RFC since many of the issues affecting the new macro system are
(or will be) addressed in other RFCs. This RFC may be expanded at a later date.
Only major change is moving from `macro!` to `macro` to declare a macro.
Fix typo (Decalrative -> Declarative)
L102: Nomencalture -> Nomenclature
L111: alterantive -> alternative
Corrected some spelling errors.
Under the heading "What the process is" a word was duplicated assumingly by
accident:

  > "The sub-team will will either close"

... the above should probably be:

  > "The sub-team will either close"
Remove duplicate word from documentation
There was an inconsistent use of "PR" and "pull request" throughout the
document. I believe that I read an article from GitHub that they suggested
the use of "pull request" instead of "PR" for the purposes of clarity.
@iopq iopq merged commit 7c02100 into iopq:master Mar 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.