Skip to content
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

Fix typos in RFC #1681 #1747

Merged
merged 2 commits into from
Sep 11, 2016
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions text/1681-macros-1.1.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ been enough to push the nightly users to stable as well.

These large projects, however, are often the face of Rust to external users.
Common knowledge is that fast serialization is done using serde, but to others
this just sounds likes "fast Rust needs nightly". Over time this persistent
this just sounds like "fast Rust needs nightly". Over time this persistent
thought process creates a culture of "well to be serious you require nightly"
and a general feeling that Rust is not "production ready".

Expand Down Expand Up @@ -207,8 +207,8 @@ pub fn double(input: TokenStream) -> TokenStream {
let source = input.to_string();

// Parse `source` for struct/enum declaration, and then build up some new
// source code representing representing a number of items in the
// implementation of the `Double` trait for the struct/enum in question.
// source code representing a number of items in the implementation of
// the `Double` trait for the struct/enum in question.
let source = derive_double(&source);

// Parse this back to a token stream and return it
Expand Down