mirror of https://github.com/rust-lang/rfcs
Edit README.md
This commit is contained in:
parent
4f235d3576
commit
c9458a6e2a
10
README.md
10
README.md
|
@ -2,6 +2,10 @@
|
||||||
|
|
||||||
[Rust RFCs]: #rust-rfcs
|
[Rust RFCs]: #rust-rfcs
|
||||||
|
|
||||||
|
The "RFC" (request for comments) process is intended to provide a consistent
|
||||||
|
and controlled path for changes to Rust (such as new features) so that all
|
||||||
|
stakeholders can be confident about the direction of the project.
|
||||||
|
|
||||||
Many changes, including bug fixes and documentation improvements can be
|
Many changes, including bug fixes and documentation improvements can be
|
||||||
implemented and reviewed via the normal GitHub pull request workflow.
|
implemented and reviewed via the normal GitHub pull request workflow.
|
||||||
|
|
||||||
|
@ -9,12 +13,6 @@ Some changes though are "substantial", and we ask that these be put through a
|
||||||
bit of a design process and produce a consensus among the Rust community and
|
bit of a design process and produce a consensus among the Rust community and
|
||||||
the [sub-team]s.
|
the [sub-team]s.
|
||||||
|
|
||||||
The "RFC" (request for comments) process is intended to provide a consistent
|
|
||||||
and controlled path for new features to enter the language and standard
|
|
||||||
libraries, so that all stakeholders can be confident about the direction the
|
|
||||||
language is evolving in.
|
|
||||||
|
|
||||||
|
|
||||||
## Table of Contents
|
## Table of Contents
|
||||||
[Table of Contents]: #table-of-contents
|
[Table of Contents]: #table-of-contents
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue