rust
/
rfcs
mirror of https://github.com/rust-lang/rfcs
1
0
Fork 0
Code Issues Releases Wiki Activity

rfc, prior-art: fix grammar, thanks @wycats

This commit is contained in:
Mazdak Farrokhzad 2018-02-15 06:18:52 +01:00
parent 9ca432a429
commit 1118f8872d
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
0000-template.md
View File

@ -55,7 +55,7 @@ Why should we *not* do this?
Discuss prior art, both the good and the bad, in relation to this proposal.
A few examples of what this can include are:
- For language, library, cargo, tools, and compiler proposals: Does this feature exists in other programming languages and what experience has their communities have had with the feature?
- For language, library, cargo, tools, and compiler proposals: Does this feature exists in other programming languages and what experience have their community had?
- For community proposals: Is this done by some other community and what were their experiences with it?
- For other teams: What lessons can we learn from what other communities have done here?
- Papers: Are there any published papers or great posts that discuss this? If you have some relevant papers to refer to, this can serve as a more detailed theoretical background.

2
text/0000-prior-art.md
View File

@ -96,7 +96,7 @@ text to the RFC template before the section *Unresolved questions*:
>
> - For language, library, cargo, tools, and compiler proposals:
> Does this feature exists in other programming languages and
> what experience has their communities have had with the feature?
> what experience have their community had?
> - For community proposals: Is this done by some other community and what
> were their experiences with it?
> - For other teams: What lessons can we learn from what other communities