forked from rust-lang/rfcs
-
Notifications
You must be signed in to change notification settings - Fork 0
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
d #1
Merged
Merged
d #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Correct typos in impl trait
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.
Fix links & reveal hidden information
Merge branch 'rvalue_static_promotion' of https://github.com/Kimundi/rfcs
Fix typos.
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.
…/rfcs into archshift-closure-to-fn-coercion
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.
Change PR to pull request
fix member path
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
d